Public bug reported:
Update to BlueZ 5.69 (or later) in Ubuntu 24.04
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for the bug report. There is no software brightness adjustment on
desktop machines. You need to adjust the brightness on the monitor
instead.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
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/bugs/2025563
Title:
System can not shutdown if system has
I downgraded to 249.11-0ubuntu3.9, 249.11-0ubuntu3.7 Because I know for
a Fact I had no issues with it, My last install was working with
249.11-0ubuntu3.9, you rolled out the update to 249.11-0ubuntu3.10 and
that is when all this started. I simply went back to an older version
after a fresh
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
** Tags removed: verification-failed-jammy
** Tags added: verification-done-jammy
--
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/bugs/2028180
Title:
[SRU][Ubuntu 22.04]
Your original bug report was about an upgrade from 249.11-0ubuntu3.9
(the previous SRU version we've now rolled back to) to
249.11-0ubuntu3.10 (the withdrawn SRU which is currently in jammy-
proposed).
> Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7),
libudev1:amd64
Public bug reported:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-
restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user
namespace restrictions for Ubuntu 23.10 are to be enabled by default via
a sysctl.d conf file in apparmor.
In
** Changed in: libwebp (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in
That was a very sane decision. Thank you. Just a minimal option that
doesn't install the desktop-recommends is good enough, I think.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
This bug was fixed in the package ubuntu-meta - 1.520
---
ubuntu-meta (1.520) mantic; urgency=medium
* Refreshed dependencies
* Make changes to restore desktop non-minimal install option (LP: #2034261)
* Added aisleriot to desktop-raspi-recommends, desktop-recommends
* Added
22.04.3LTS -Ubuntu
Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.7)
Camera any kind, I tried both my NikonD5600 and Olympus OM-D E-M5, which both
work again as they should and did before this mess started.
--
You received this
Public bug reported:
My home network comprises many VLANs managed by `systemd-
networkd`/`netplan`. Those VLANs are then used as parent interfaces for
LXD networks. Whenever `systemd-networkd` is restarted (i.e: post-
update), my whole network breaks because all the unmanaged bridges lose
their
To reproduce your problem, can you specify steps to reproduce (with
version numbers)? Which Ubuntu image did you use for installation? To
which udev version did you downgrade? Which camera do you have and how
did you connect it to your computer?
--
You received this bug notification because you
350 MiB for /boot is a little bit too small especially when you have
nvidia drivers installed. You could try compress the initramfs with xz
with a high level.
I am marking this bug as invalid since is it caused by a full /boot
partition.
** Changed in: initramfs-tools (Ubuntu)
Status: New
Tried all your steps, they kept breaking my system more and more. Had to
re-install ubutnu from liveusb, installed synaptic downgraded udev and
locked verison, read markings, reboot, update, upgrade reboot, get my
audio and bluetooth up and working again reboot, everything works, its
your udev
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Looking at the attached, it looks like I'm out of space on /boot again.
It looks like maybe
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154 intended to
fix this, but I seem to only have room for two kernels in /boot.
--
You received this bug notification because you are a member of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2036124
Title:
package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
Public bug reported:
A crash notification popped up when I was not doing anything so I'm not
sure what caused it. I hope the automatically-added debug information
contains something useful.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
> pipewire:i386
This explains the loss of audio after downgrade.
Unfortunately the semantics of package pins do not match on foreign-arch
packages without explicitly listing the arch name.
And for some reason, you had pipewire installed on your system for the wrong
architecture.
Julian's apt
Has this been addressed(*)? If so, could the respective commit ID's be
posted here for reference, please?
(*) https://sourceware.org/pipermail/libc-alpha/2023-June/148812.html would
suggest that it was but perhaps not entirely?
--
You received this bug notification because you are a member
> When working with ubuntu core or ubuntu core desktop, neither
> /etc/default/locale
> nor /etc/default/keyboard are modificable
They should be. This needs to be fixed in Ubuntu Core, not in systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
On Thu, Sep 14, 2023 at 07:52:49PM -, Philip A Swiderski Jr wrote:
> PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO.
You didn't show the output of the apt command or otherwise confirm, but I
did stipulate that:
> This should offer to downgrade all binary packages from the systemd source
>
PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. No I have to do a fresh
install. You guys really need to pay better attention to your updates,
this is a system break not an upgrade. Im really not happy, and as I
love ubuntu, and I really appreciate all the hard work you guys all put
into making
A shorter version that avoids the preferences file is:
sudo apt update && sudo apt install --no-remove '?installed?source-
package(^systemd$)/jammy-updates'
Unless something else depends on a newer systemd in which case both
don't work, but essentially this should.
--
You received this bug
Please install the attached apt preferences file to
/etc/apt/preferences.d/ (as root) and then run 'sudo apt update && sudo
apt upgrade'.
This should offer to downgrade all binary packages from the systemd
source package to the current jammy-updates versions, without removing
any other packages.
More interesting info, so I just tested digiKam-8.1.0-x86-64.appimage
and it Can talk to my camera, but the Installed digikam package CAN NOT
TALK, but I still can not use gphoto2 to stream my camera, nor can I use
entangle to use my camera tethered. Because they can not talk to the
camera, I
Dont know if this helps, but here is a complete list of installed
libnova-0.16-0 install
libgpg-error-l10n install
dpkginstall
kerneloops install
libkf5quickaddons5 install
golang-golang-x-term-devinstall
fontconfig:i386
I've tested the kernel from focal-proposed, with the systemd packages
from my personal PPA (as the systemd patches aren't yet available in
focal-proposed).
All test variants from the rep-tmpfs.sh script ran succesfully, and
general smoke testing revealed no further issues.
ubuntu@z-rotomvm35:~$
Tried to stream with debug,
gphoto2 --stdout --capture-movie --debug | ffmpeg -i - -vcodec rawvideo
-pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0
0.000107 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000131 main
In order to roll back udev in Synaptic, I get
To Be Removed
libgstreamer-plugins-base1.0-dev
libgudev-1.0-dev
libnm0:i386
libpipewire-0.3-0:i386
libpipewire-0.3-modules:i386
libspa-0.2-modules:i386
libudev-dev
libudev1:i386
pipewire:i386
steam:i386
To be downgraded
libudev1
I cant roll back or
Public bug reported:
No sound. Impossible to install the driver for hp 850 G6
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion:
I downloaded your rules and used you commands to move it, I rebooted and
same issue, here is the result of gphoto2 --debug
gphoto2 --debug
0.000101 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000114 main
The backtrace unfortunately doesn't provide any information that points
to how this could be a systemd problem. The crashing thread appears to
be:
Thread 12 (Thread 0x7f50a9f2e640 (LWP 282533) "ThreadPoolServi"):
#1 0x7f50de277845 in buffered_vfprintf (s=0x7f50de41a6a0
<_IO_2_1_stderr_>,
Here is some backtrace of digikam crashing after trying to import photos from
camera,
Application: digiKam (digikam), signal: Segmentation fault
[KCrash Handler]
#4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#5 0x7f50de2a8603 in __GI___strdup (s=0x0) at
YES this bug persists after (a) sudo systemctl daemon-reexec, and/or (b)
reboot
--
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/bugs/2035406
Title:
udev update has broken
Rebooting does nothing, same issue. systemctl daemon-reexec does
nothing, same issue no one can talk to my camera, I tried a different
camera same issue, lsusb cameras show up just fine so usb's are working,
but something happens with that update that caused a roadblock between
usb and other
Dropping the rls-ll-incoming tag, which is an incoming queue for
Canonical teams to assess prioritization. Since the only open task is
against a universe package, it does not apply here.
** Tags removed: rls-ll-incoming
--
You received this bug notification because you are a member of Ubuntu
** Also affects: ubuntu-meta (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Also affects: ubuntu-release-upgrader (Ubuntu Mantic)
Importance: Critical
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
History is a little bit tricky, patch
hhttps://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749
(applied in current debdiff) was merged to the master branch but probably was
lost while repository was moving to a "newlib".
Last released version
** Patch added: "gst-plugins-bad1.0_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+attachment/5700925/+files/gst-plugins-bad1.0_focal.debdiff
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-37329
** Tags added: community-security
This bug was fixed in the package openssh - 1:8.9p1-3ubuntu0.4
---
openssh (1:8.9p1-3ubuntu0.4) jammy; urgency=medium
* d/p/fix-authorized-principals-command.patch: Fix the situation where
sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand
is also set by
The verification of the Stable Release Update for openssh has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8.5
---
openssh (1:9.0p1-1ubuntu8.5) lunar; urgency=medium
* d/p/fix-authorized-principals-command.patch: Fix the situation where
sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand
is also set by
The Europe/Kiev symlink is now in tzdata-legacy, so we can just depend
on that for these autopkgtests.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox-esr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libwebp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
** Changed in: gst-plugins-bad1.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/2035585
Title:
Versions in Ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/amd64/s/systemd/20230912_054033_0b699@/log.gz
Basically every upstream test fails with odd errors. Early in the tests,
a common default.img is supposed to be built, but this fails:
2614s I:
Okay. I am closing this bug report.
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
We may as well close this issue, I don't have that laptop any more, I
don't work for Canonical any more and the boot speed regressions seem to
have fallen off the CTO's "must do priority radar" otherwise this kind
of regression would have had more engineering time devoted to it.
--
You received
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
cp: cannot stat '/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf':
No such file or directory
This file is part of the ttf-dejavu-core package (on Ubuntu 16.04).
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
mv: impossible d'évaluer '/boot/initrd.img-4.4.0-38-generic.new': Aucun
fichier ou dossier de ce type
deepl trantlates it to:
mv: unable to evaluate
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
Public bug reported:
Hi,
is this a cache bug? The packages are installed, but "apt list
--upgradable" say's no, the are not installed.
root@minion:~# apt list --upgradable
Listing... Done
uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64
[upgradable from:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
update-initramfs: Generating /boot/initrd.img-4.4.0-28-generic
/etc/initramfs-tools/hooks/reiserfsprogs: line 3:
./usr/share/initramfs-tools/hook-functions: Permission denied
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I re-assigned your bug report against the linux package.
** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
pigz: abort: write error on (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
So generating the initramfs fails because your boot partition is full.
Please
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug has been marked a duplicate of bug 798414
update-initramfs should produce a more helpful error message when there
isn't enough free space--or provide an automatic tool for removal of old
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
cp: error writing
'/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/vega10_uvd.bin': No space
left on device
cp: error writing
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
update-initramfs: Generating /boot/initrd.img-5.19.0-35-generic
grep: /boot/config-5.19.0-35-generic: No such file or directory
W: zstd compression (CONFIG_RD_ZSTD) not
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
sync: error syncing '/boot/initrd.img-5.19.0-41-generic': Input/output
error
Input/output error indicates a problem with your storage device. I
recommend performing a back up
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
Sadly there is no error message explaining the exit code 1. Can you edit
/usr/share/initramfs-tools/hooks/fuse
** Changed in: oem-priority
Status: Fix Released => Confirmed
--
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/bugs/2025563
Title:
System can not shutdown if system has
Okay, so looking again at the diff from 249.11-0ubuntu3.9 to
249.11-0ubuntu3.10[1], the only udev change is a new symlink for nvme
devices. It seems very unlikely that this is related. The only other
change that would be suspicious to me is the systemd.postinst change,
i.e. requesting a reboot for
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/2035585
Title:
Versions in Ubuntu 20.04,
--- Comment From christian.r...@de.ibm.com 2023-09-14 03:15 EDT---
First, reproduced the behaviour of the problem as described and encountered the
segmentation fault situation as described.
Wrote out the coredump with coredumpctl dump and saw from the call stack the
reported problem was
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in
I'm guessing the HDMI port is connected to the Nvidia GPU, it usually is
on a hybrid laptop. And I'm seeing that you don't have a proper driver
for the Nvidia GPU installed. Please open the 'Additional Drivers' app
to install a supported Nvidia driver.
** Package changed: xorg (Ubuntu) => ubuntu
80 matches
Mail list logo
