@bugoff: your bug is the bug related to tracker-extract:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2055761
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/204
Public bug reported:
i've been investigating bugs of the gstreamer backend of qt
(QTBUG-122424, QTBUG-122423). it seems that we run into a pulseaudio bug
that has been fixed in pulseaudio-17.
what would it take to backport the corresponding fix?
https://gitlab.freedesktop.org/pulseaudio/pulseaudi
Noble is now shipping with SimpleDRM enabled in kernel 6.8, so the next
step is comment #49 (which would also resolve bug 1869655).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/
Having the same issue as in #7 (id: ‘polkitd’: no such user, chown:
invalid group: ‘root:polkitd’). Managed to apply workaround to move with
the test upgrade from this stuck place by creating polkitd system group
using `groupadd -r polkitd`.
--
You received this bug notification because you are
don't know how to add multiple files at ones
** Attachment added: "Screenshot from 2024-03-03 22-57-06.png"
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+attachment/5752202/+files/Screenshot%20from%202024-03-03%2022-57-06.png
--
You received this bug notification because
don't know how to add multiple files at ones
** Attachment added: "IMG_20240304_014352.jpg"
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+attachment/5752201/+files/IMG_20240304_014352.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seede
still reproducible on my dell xps 13 9360 with the latest 2024-02-29 17:40 build
it is also crushes at the end of installation when you launch the installer
manually
** Attachment added: "IMG_20240304_014304.jpg"
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+attachment/575
I applied the patch and ran `update-initramfs -u` with
`/lib/libc6-prof/x86_64-linux-gnu` at the front of my dynamic linker
search path and it seemed to work. Even installed a new kernel update
with the patch in place and the system rebooted into the new kernel.
That's better than before, where the
** Summary changed:
- Wine program crashes with unhandled page fault on startup
+ [regression] Wine program crashes with unhandled page fault on startup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://
** Tags added: rls-nn-incoming
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2055806
T
do-release-upgrade log
** Attachment added: "dist-upgrade-screenlog.0.txt"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055825/+attachment/5752088/+files/dist-upgrade-screenlog.0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Upgrade from 20.04 to 22.04 failed with "Fatal: unexpected error from
getentropy: Invalid argument". We have fips-updates enabled thru Ubuntu
pro subscription. Tried to upgrade from 18.04 to 22.04. Upgrade from
18.04 to 204 is successful but upgrade from 20.04 to 22.04 failed.
I believe you now have sources.list in the old format
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Sta
That is great news, I'm glad we've identified the root cause of the
problem and you have successfully resolved it.
I will mark this bug as invalid since, while the dnsmasq update did
change behaviour, the behaviour change revealed a configuration issue
rather than being an actual regression.
Than
I deleted the files in the /etc/apt/sources.list.d and then it opened normally
except all the sources where unselected.
When software and properties is opened again just tick the appropriate sources
from the first tab and select close and reload at the prompt. After that it has
worked normally a
I've changed the Unit files for the mount and automount points and will
see if this was the cause of the unit ordering issue. I commented out
the Requires= files and just left the After= files to create a softer
dependency tree.
```
''# cat mnt-xbmc\\x2ddata.mount''
[Unit]
Description=mount cifs
I'm looking at the journalctl logs for systemd-tmpfiles-setup.service
and sysinit.target/start and it shows up that one of the mount and
automount units that I created might have caused a problem and systemd
somehow deleted the start events for systemd-tmpfiles-
setup.service/start event.
This lin
When the /run/sshd/ directory exits and looks good.
```
'''stat /run/sshd'''
File: /run/sshd
Size: 40 Blocks: 0 IO Block: 4096 directory
Device: 0,25Inode: 1786Links: 2
Access: (0755/drwxr-xr-x) Uid: (0/root) Gid: (0/root)
Access: 2024-03
More discussion threads regarding this issue.
This is an old one from 16.04 before ssh socket activation.
https://askubuntu.com/questions/1110828/ssh-failed-to-start-missing-
privilege-separation-directory-var-run-sshd
Another older report from 5-years ago from 16.04.05 again.
https://askubuntu.
Found this reference also to this folder.
```
''man sshd''
/run/sshd
chroot(2) directory used by sshd during privilege separation in
the pre‐authentication phase. The directory should not contain any files and
must be owned by root and not group or world‐writable.
```
--
You
** Tags added: packaging systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2055806
Title:
sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
priv
This is a follow-up to the problems reported in the following thread
that already discussed an issue with socket activation for the
ssh.service.
SSHd now uses socket-based activation (Ubuntu 22.10 and later)
https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-late
Public bug reported:
Symptom: ssh.service is not running and not accepting new SSH
connections and returns socket closed error upon attempted connection.
ssh.service shows a failed with error message "Missing privilege
separation directory: /run/sshd".
The following line is needed in the SystemD
23 matches
Mail list logo
