On 24.04 Noble and my Bose QC45 headphones won't reconnect after reboot.
Created a bluez package with a patched src/adapter.c using:
https://launchpadlibrarian.net/757506303/bluez-fix-address.patch
(build instructions:
https://gist.github.com/bitmand/76f7bd5cbb22cb51ef1e82db320eadc6 )
After ins
** Summary changed:
- kworker takes a lot of CPU
+ loop of firmware/acpi/interrupts/gpe03 takes a lot of CPU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861419
Title:
loop of fir
This is fixed in Plucky 6.12.0-7.7 bootstrap kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap
** Changed in: linux (Ubuntu Plucky)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Plucky)
Status: Fix Released => Fix Committed
--
You rece
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.
Public bug reported:
This commit is somehow got into focal:linux 2025.01.13 cycle via
upstream tags. We need to remove this as it is removed before from
s2024.10.28 cycle. This commit causes ubuntu_kselftests_ftrace tests to
fail.
** Affects: linux (Ubuntu)
Importance: Undecided
Sta
Interesting, there are reports on raspberry pi as well, when putting
videos in fullscreen:
https://forums.raspberrypi.com/viewtopic.php?t=357826
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2093338
Title:
Keyboard not working after kernel upgrade
St
Same problem here. The only additional information I can provide is that
it works as expected in 6.8.0-49-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2093338
Title:
Keyboard
Public bug reported:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was fo
Public bug reported:
[Impact]
No sound output from one of the speaker on HP ZBook[cs35l56]
[Fix]
This linux-firmware commit is required
5e1e0ae5 cirrus: cs35l56: Correct some links to address the correct amp instance
[Test]
1. Boot to OS on HP ZBook with cs35l56 codec
2. The sound can be output
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Attachment added: "iscsi-init error.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095321/+attachment/5853039/+files/iscsi-init%20error.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Summary changed:
- [Ubuntu 24.04.01] Observing busy box errors while configuring ISCSI on top of
UBUNTU OS
+ [Ubuntu 24.04.01] Observing busy box errors while booting Ubuntu OS on ISCSI
LUN
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
On Dell PowerEdge system Observing errors while booting Ubuntu OS to
ISSCI LUN
Steps to Reproduce: -
Step 1 - Configure iscsi lun on server
step 2 - reboot and establish the connection
Step 3 - Start intallation
Step 4 - Pass the parameteres to discover iscsi
Step 5 - select
Troubleshooting & Observations:
1. Observed no issue in communication between initiator and target, and no
network ping drops observed.
2. attempted rescan scsi devices
3. attempted fsck
4. manually modprobe iscsi_ibft
5. passed iscsistart -N & iscsistart -b
ended up with same outcome and the OS
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP:
I can confirm that kernel 6.8.0-51 does not solve the problem. I now
allowed Software Updater to update the kernel to version 6.8.0-51 . The
laptop is unable to boot with the new kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Found this thread last year due to a new problem with NFS timeout errors
on my server. That was after upgrade from 5.15.0-122-generic to
6.8.0-45-generic. Last week I upgraded to 6.8.0-51-generic. Immediately
got NFS timeout errors during the builds. Now back again at
5.15.0-122-generic, which give
drm/amd/display: Allow backlight to go below AMDGPU_DM_DEFAULT_MIN_BACKLIGHT
The issue with panel power savings compatibility below
`AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` happens at
`AMDGPU_DM_DEFAULT_MIN_BACKLIGHT` as well.
That issue will be fixed separately, so don't prevent the backlight
brightness
The 2 patch above is available in mainline kernel 6.11.3
The issues is originated from:
https://gitlab.freedesktop.org/drm/amd/-/issues/3020
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/104 created
for review.
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Oracular)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Plucky)
St
The v5.15.175 upstream stable release for Jammy brings crucial updates
and improvements, ensuring better performance and stability for users.
Staying updated with the latest releases is key for optimizing system
functionality. If you're sharing tech updates on your site or blog,
https://poehub.org/
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
31 matches
Mail list logo
