This indicates the 6.17 kernel did not install/configure correctly. Usually, it is caused by either:
1. An external kernel module not building. Check output of:
sudo dkms status
2. bug 2115148
If you cannot figure it out, run the following command and copy/paste output:
sudo apt dist-upgrade
** Package changed: linux (Ubuntu) => linux-hwe-6.17 (Ubuntu)
** Changed in: linux-hwe-6.17 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147294
Title:
Regression: Ubuntu 24.04 HWE kernel 6.17 causes multiple device/input
failures after reboot
Status in linux-hwe-6.17 package in Ubuntu:
Incomplete
Bug description:
After updating Ubuntu 24.04 LTS to a recent HWE 6.17 kernel, the
system developed a serious regression after reboot.
What I expected to happen:
The system should boot normally, with working input devices and peripherals, as before the update.
What happened instead:
After reboot, the system became partially unusable. At minimum, the internal keyboard stopped working. Other peripherals also appeared to be affected, including the microphone. The mouse still worked, and the display was visible, but I could not fully determine the exact extent of the breakage from the broken graphical session alone.
Why I am reporting this generically:
I cannot confidently identify every subsystem that failed. The issue looked broader than a single device failure, so I am reporting it as a kernel regression affecting peripherals / input / general usability rather than only one specific component.
Regression:
Yes. The problem appeared after updating to the HWE 6.17 kernel series, and the system recovered after removing the problematic 6.17 kernels and going back to the stable generic kernel.
Recovery / workaround:
I recovered the machine from an Ubuntu Live USB. I mounted the installed system, entered it through chroot, removed the problematic 6.17 kernel packages, reinstalled the stable generic kernel, regenerated initramfs, and updated GRUB. After reboot, the system started correctly again on 6.8.0-107-generic.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-107-generic 6.8.0-107.107
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
Uname: Linux 6.8.0-107-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: teygeta 2480 F.... wireplumber
/dev/snd/controlC2: teygeta 2480 F.... wireplumber
/dev/snd/controlC0: teygeta 2480 F.... wireplumber
/dev/snd/seq: teygeta 2476 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 5 11:05:30 2026
InstallationDate: Installed on 2026-03-15 (21 days ago)
InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210)
MachineType: MSI MS-7A65
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-ghostty
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-107-generic root=UUID=367ddc98-d2ca-421e-aec3-cebfb331cc7b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-107-generic N/A
linux-backports-modules-6.8.0-107-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M GAMING PRO (MS-7A65)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd07/24/2018:br5.12:svnMSI:pnMS-7A65:pvr1.0:rvnMSI:rnB250MGAMINGPRO(MS-7A65):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A65
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.17/+bug/2147294/+subscriptions
воскресенье
Re: [Bug 2146485] Re: IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops at i8042 kernel driver level
When you report to Lenovo, it's an important data point that two users on
two different OS are experiencing this same issue. If you share the
support request, I'll post on it there, as well.
--
Advanced Applications
Rod Barnes
On Sun, Apr 5, 2026, 7:01 AM Rod Barnes <advappsw@gmail.com> wrote:
> The BIOS was going to be my next effort. :-(
> Good luck. Report back if you find a solution, as will I.
>
>
> --
> Advanced Applications
> Rod Barnes
>
> On Sat, Apr 4, 2026, 12:15 PM Cuchet Léo <2146485@bugs.launchpad.net>
> wrote:
>
>> Hello,
>>
>> Unfortunately, I already am running the latest version of the BIOS
>> (R0CN27WW).
>>
>> I checked BIOS historical modification from their Readme file, but it
>> doesn't specify any modifications about keyboard behaviour in the EC
>> Firmware part.
>>
>> I think I'll end up contacting Lenovo support directly, and hope they
>> have a fix for it.
>>
>> But still, thank you for trying to help !
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2146485
>>
>> Title:
>> IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
>> at i8042 kernel driver level
>>
>> Status in linux package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
>> intermittently begins dropping keystrokes after a variable uptime
>> (sometimes hours, sometimes days). The issue clears on reboot and does
>> not persist across power cycles.
>>
>> Hardware:
>> System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
>> BIOS: R0CN22WW
>> OS: Linux Mint 22.3
>> Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
>>
>> Diagnosis:
>> evtest confirms keystroke drops are occurring at the kernel input
>> driver level, not in X11 or the compositor
>>
>> dmesg shows no i8042 errors during affected sessions
>>
>> /proc/interrupts shows normal i8042 interrupt counts during the
>> problem
>>
>> Memory, swap, CPU load, and thermals are all normal during affected
>> sessions
>>
>> The i8042 module is built-in and cannot be reloaded to recover without
>> a full reboot
>>
>> Boot parameter i8042.nopnp (added based on kernel warning at boot:
>> "PS/2 appears to have AUX port disabled, if this is incorrect please
>> boot with i8042.nopnp") improved perceived keyboard latency but did
>> not prevent recurrence of drops
>>
>> TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
>> "on" during an affected session did not resolve the issue
>>
>> $ cat /proc/interrupts | grep i8042
>> 1: 0 28512 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 0 IR-IO-APIC 1-edge i8042
>>
>> Kernel boot messages:
>> i8042: PNP detection disabled
>> serio: i8042 KBD port at 0x60,0x64 irq 1
>> input: AT Translated Set 2 keyboard as
>> /devices/platform/i8042/serio0/input/input2
>> Current kernel cmdline:
>> quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
>>
>> Expected behavior: Keyboard input should be reliable throughout a
>> session without requiring a reboot to restore normal function.
>>
>> Workaround: Reboot restores normal keyboard function until the issue
>> recurs.
>>
>> Possibly significant point: I am a fast typist but I experience this
>> even when typing very slowly.
>>
>> Attached archive contains:
>> $ cat /proc/version_signature > ~/version.log
>> $ sudo lspci -vnvn > ~/lspci-vnvn.log
>> $ sudo dmesg > ~/dmesg.log
>> $ cat /proc/interrupts > ~/interrupts.log
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
>>
>>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
two different OS are experiencing this same issue. If you share the
support request, I'll post on it there, as well.
--
Advanced Applications
Rod Barnes
On Sun, Apr 5, 2026, 7:01 AM Rod Barnes <advappsw@gmail.com> wrote:
> The BIOS was going to be my next effort. :-(
> Good luck. Report back if you find a solution, as will I.
>
>
> --
> Advanced Applications
> Rod Barnes
>
> On Sat, Apr 4, 2026, 12:15 PM Cuchet Léo <2146485@bugs.launchpad.net>
> wrote:
>
>> Hello,
>>
>> Unfortunately, I already am running the latest version of the BIOS
>> (R0CN27WW).
>>
>> I checked BIOS historical modification from their Readme file, but it
>> doesn't specify any modifications about keyboard behaviour in the EC
>> Firmware part.
>>
>> I think I'll end up contacting Lenovo support directly, and hope they
>> have a fix for it.
>>
>> But still, thank you for trying to help !
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2146485
>>
>> Title:
>> IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
>> at i8042 kernel driver level
>>
>> Status in linux package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
>> intermittently begins dropping keystrokes after a variable uptime
>> (sometimes hours, sometimes days). The issue clears on reboot and does
>> not persist across power cycles.
>>
>> Hardware:
>> System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
>> BIOS: R0CN22WW
>> OS: Linux Mint 22.3
>> Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
>>
>> Diagnosis:
>> evtest confirms keystroke drops are occurring at the kernel input
>> driver level, not in X11 or the compositor
>>
>> dmesg shows no i8042 errors during affected sessions
>>
>> /proc/interrupts shows normal i8042 interrupt counts during the
>> problem
>>
>> Memory, swap, CPU load, and thermals are all normal during affected
>> sessions
>>
>> The i8042 module is built-in and cannot be reloaded to recover without
>> a full reboot
>>
>> Boot parameter i8042.nopnp (added based on kernel warning at boot:
>> "PS/2 appears to have AUX port disabled, if this is incorrect please
>> boot with i8042.nopnp") improved perceived keyboard latency but did
>> not prevent recurrence of drops
>>
>> TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
>> "on" during an affected session did not resolve the issue
>>
>> $ cat /proc/interrupts | grep i8042
>> 1: 0 28512 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 0 0 IR-IO-APIC 1-edge i8042
>>
>> Kernel boot messages:
>> i8042: PNP detection disabled
>> serio: i8042 KBD port at 0x60,0x64 irq 1
>> input: AT Translated Set 2 keyboard as
>> /devices/platform/i8042/serio0/input/input2
>> Current kernel cmdline:
>> quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
>>
>> Expected behavior: Keyboard input should be reliable throughout a
>> session without requiring a reboot to restore normal function.
>>
>> Workaround: Reboot restores normal keyboard function until the issue
>> recurs.
>>
>> Possibly significant point: I am a fast typist but I experience this
>> even when typing very slowly.
>>
>> Attached archive contains:
>> $ cat /proc/version_signature > ~/version.log
>> $ sudo lspci -vnvn > ~/lspci-vnvn.log
>> $ sudo dmesg > ~/dmesg.log
>> $ cat /proc/interrupts > ~/interrupts.log
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
>>
>>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
Re: [Bug 2146485] Re: IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops at i8042 kernel driver level
The BIOS was going to be my next effort. :-(
Good luck. Report back if you find a solution, as will I.
--
Advanced Applications
Rod Barnes
On Sat, Apr 4, 2026, 12:15 PM Cuchet Léo <2146485@bugs.launchpad.net>
wrote:
> Hello,
>
> Unfortunately, I already am running the latest version of the BIOS
> (R0CN27WW).
>
> I checked BIOS historical modification from their Readme file, but it
> doesn't specify any modifications about keyboard behaviour in the EC
> Firmware part.
>
> I think I'll end up contacting Lenovo support directly, and hope they
> have a fix for it.
>
> But still, thank you for trying to help !
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2146485
>
> Title:
> IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
> at i8042 kernel driver level
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
> intermittently begins dropping keystrokes after a variable uptime
> (sometimes hours, sometimes days). The issue clears on reboot and does
> not persist across power cycles.
>
> Hardware:
> System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
> BIOS: R0CN22WW
> OS: Linux Mint 22.3
> Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
>
> Diagnosis:
> evtest confirms keystroke drops are occurring at the kernel input driver
> level, not in X11 or the compositor
>
> dmesg shows no i8042 errors during affected sessions
>
> /proc/interrupts shows normal i8042 interrupt counts during the
> problem
>
> Memory, swap, CPU load, and thermals are all normal during affected
> sessions
>
> The i8042 module is built-in and cannot be reloaded to recover without
> a full reboot
>
> Boot parameter i8042.nopnp (added based on kernel warning at boot:
> "PS/2 appears to have AUX port disabled, if this is incorrect please
> boot with i8042.nopnp") improved perceived keyboard latency but did
> not prevent recurrence of drops
>
> TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
> "on" during an affected session did not resolve the issue
>
> $ cat /proc/interrupts | grep i8042
> 1: 0 28512 0 0 0 0
> 0 0 0 0 0 0
> 0 0 0 0 IR-IO-APIC 1-edge i8042
>
> Kernel boot messages:
> i8042: PNP detection disabled
> serio: i8042 KBD port at 0x60,0x64 irq 1
> input: AT Translated Set 2 keyboard as
> /devices/platform/i8042/serio0/input/input2
> Current kernel cmdline:
> quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
>
> Expected behavior: Keyboard input should be reliable throughout a
> session without requiring a reboot to restore normal function.
>
> Workaround: Reboot restores normal keyboard function until the issue
> recurs.
>
> Possibly significant point: I am a fast typist but I experience this
> even when typing very slowly.
>
> Attached archive contains:
> $ cat /proc/version_signature > ~/version.log
> $ sudo lspci -vnvn > ~/lspci-vnvn.log
> $ sudo dmesg > ~/dmesg.log
> $ cat /proc/interrupts > ~/interrupts.log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
>
>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
Good luck. Report back if you find a solution, as will I.
--
Advanced Applications
Rod Barnes
On Sat, Apr 4, 2026, 12:15 PM Cuchet Léo <2146485@bugs.launchpad.net>
wrote:
> Hello,
>
> Unfortunately, I already am running the latest version of the BIOS
> (R0CN27WW).
>
> I checked BIOS historical modification from their Readme file, but it
> doesn't specify any modifications about keyboard behaviour in the EC
> Firmware part.
>
> I think I'll end up contacting Lenovo support directly, and hope they
> have a fix for it.
>
> But still, thank you for trying to help !
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2146485
>
> Title:
> IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
> at i8042 kernel driver level
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
> intermittently begins dropping keystrokes after a variable uptime
> (sometimes hours, sometimes days). The issue clears on reboot and does
> not persist across power cycles.
>
> Hardware:
> System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
> BIOS: R0CN22WW
> OS: Linux Mint 22.3
> Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
>
> Diagnosis:
> evtest confirms keystroke drops are occurring at the kernel input driver
> level, not in X11 or the compositor
>
> dmesg shows no i8042 errors during affected sessions
>
> /proc/interrupts shows normal i8042 interrupt counts during the
> problem
>
> Memory, swap, CPU load, and thermals are all normal during affected
> sessions
>
> The i8042 module is built-in and cannot be reloaded to recover without
> a full reboot
>
> Boot parameter i8042.nopnp (added based on kernel warning at boot:
> "PS/2 appears to have AUX port disabled, if this is incorrect please
> boot with i8042.nopnp") improved perceived keyboard latency but did
> not prevent recurrence of drops
>
> TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
> "on" during an affected session did not resolve the issue
>
> $ cat /proc/interrupts | grep i8042
> 1: 0 28512 0 0 0 0
> 0 0 0 0 0 0
> 0 0 0 0 IR-IO-APIC 1-edge i8042
>
> Kernel boot messages:
> i8042: PNP detection disabled
> serio: i8042 KBD port at 0x60,0x64 irq 1
> input: AT Translated Set 2 keyboard as
> /devices/platform/i8042/serio0/input/input2
> Current kernel cmdline:
> quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
>
> Expected behavior: Keyboard input should be reliable throughout a
> session without requiring a reboot to restore normal function.
>
> Workaround: Reboot restores normal keyboard function until the issue
> recurs.
>
> Possibly significant point: I am a fast typist but I experience this
> even when typing very slowly.
>
> Attached archive contains:
> $ cat /proc/version_signature > ~/version.log
> $ sudo lspci -vnvn > ~/lspci-vnvn.log
> $ sudo dmesg > ~/dmesg.log
> $ cat /proc/interrupts > ~/interrupts.log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
>
>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
[Bug 2146761] Re: Bluetooth audio headset regression on 7.0.0-10-generic: Shokz OpenComm2 disconnects, works on 6.19.0-6-generic
Affects me with 7.0.0-10-generic and Bose NC 700 on ThinkPad T14 Gen 1.
Not sure how to build bluetooth.ko to check the fix. Sorry.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
Not sure how to build bluetooth.ko to check the fix. Sorry.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146761
Title:
Bluetooth audio headset regression on 7.0.0-10-generic: Shokz
OpenComm2 disconnects, works on 6.19.0-6-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
After the system update on March 29, 2026, my Bluetooth audio headset
(Shokz OpenComm2 / OpenComm2 by Shokz_II) stopped working on kernel
7.0.0-10-generic.
The headset either disconnects within about 10 seconds after
connect, or the connection is canceled and audio profiles fail to come
up.
If I reboot the same machine into the previous kernel
6.19.0-6-generic, the headset works again without changing userspace
packages or pairing state.
This looks like a kernel regression in 7.0.0-10-generic.
Working kernel:
6.19.0-6-generic
Linux book 6.19.0-6-generic #6-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 18 15:48:21 UTC 2026 x86_64 GNU/Linux
Broken kernel:
7.0.0-10-generic
From previous boot kernel log:
Linux version 7.0.0-10-generic (buildd@lcy02-amd64-051) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-15ubuntu2) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #10-Ubuntu SMP
PREEMPT_DYNAMIC Thu Mar 19 10:24:42 UTC 2026 (Ubuntu 7.0.0-10.10-generic 7.0.0-rc4)
Userspace versions at the time:
bluez 5.85-4
pipewire 1.6.2-1ubuntu1
wireplumber 0.5.13-1ubuntu1
gnome-shell 50.0-0ubuntu2
same userspace + new kernel fails.
Steps to reproduce:
1. Boot kernel 7.0.0-10-generic.
2. Power on the Shokz OpenComm2 headset.
3. Connect it from GNOME Settings or with bluetoothctl.
4. Wait a few seconds.
Expected result:
The headset should stay connected and its audio profile should become usable.
Actual result:
- Another Bluetooth device (Logitech Pebble mouse) still works, so this is not a total Bluetooth failure.
- I tested re-pairing the headset and rebooting the headset; that did not help on 7.0.0-10-generic.
- I tested disabling Bluetooth headset autoswitch behavior in WirePlumber; that did not fix it on 7.0.0-10-generic.
- There is no GNOME Shell crash here; this does not appear to be the old gnome-shell bug 2138654.
Relevant bluetoothd log lines from the broken boot:
- src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to A0:0C:C3:E1:3F:7C: Connection reset by peer (104)
- src/service.c:btd_service_connect() a2dp-sink profile connect failed for A0:0C:C3:E1:3F:7C: Device or resource busy
- profiles/audio/avdtp.c:avdtp_connect_cb() connect to A0:0C:C3:E1:3F:7C: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection refused (111)
- profiles/audio/avctp.c:avctp_connect_cb() HUP or ERR on socket: Connection timed out (110)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146761/+subscriptions
[Bug 2147294] [NEW] Regression: Ubuntu 24.04 HWE kernel 6.17 causes multiple device/input failures after reboot
Public bug reported:
After updating Ubuntu 24.04 LTS to a recent HWE 6.17 kernel, the system
developed a serious regression after reboot.
What I expected to happen:
The system should boot normally, with working input devices and peripherals, as before the update.
What happened instead:
After reboot, the system became partially unusable. At minimum, the internal keyboard stopped working. Other peripherals also appeared to be affected, including the microphone. The mouse still worked, and the display was visible, but I could not fully determine the exact extent of the breakage from the broken graphical session alone.
Why I am reporting this generically:
I cannot confidently identify every subsystem that failed. The issue looked broader than a single device failure, so I am reporting it as a kernel regression affecting peripherals / input / general usability rather than only one specific component.
Regression:
Yes. The problem appeared after updating to the HWE 6.17 kernel series, and the system recovered after removing the problematic 6.17 kernels and going back to the stable generic kernel.
Recovery / workaround:
I recovered the machine from an Ubuntu Live USB. I mounted the installed system, entered it through chroot, removed the problematic 6.17 kernel packages, reinstalled the stable generic kernel, regenerated initramfs, and updated GRUB. After reboot, the system started correctly again on 6.8.0-107-generic.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-107-generic 6.8.0-107.107
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
Uname: Linux 6.8.0-107-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: teygeta 2480 F.... wireplumber
/dev/snd/controlC2: teygeta 2480 F.... wireplumber
/dev/snd/controlC0: teygeta 2480 F.... wireplumber
/dev/snd/seq: teygeta 2476 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 5 11:05:30 2026
InstallationDate: Installed on 2026-03-15 (21 days ago)
InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210)
MachineType: MSI MS-7A65
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-ghostty
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-107-generic root=UUID=367ddc98-d2ca-421e-aec3-cebfb331cc7b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-107-generic N/A
linux-backports-modules-6.8.0-107-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M GAMING PRO (MS-7A65)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd07/24/2018:br5.12:svnMSI:pnMS-7A65:pvr1.0:rvnMSI:rnB250MGAMINGPRO(MS-7A65):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A65
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug kernel-bug noble wayland-session
** Attachment added: "version.log"
https://bugs.launchpad.net/bugs/2147294/+attachment/5958742/+files/version.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147294
Title:
Regression: Ubuntu 24.04 HWE kernel 6.17 causes multiple device/input
failures after reboot
Status in linux package in Ubuntu:
New
Bug description:
After updating Ubuntu 24.04 LTS to a recent HWE 6.17 kernel, the
system developed a serious regression after reboot.
What I expected to happen:
The system should boot normally, with working input devices and peripherals, as before the update.
What happened instead:
After reboot, the system became partially unusable. At minimum, the internal keyboard stopped working. Other peripherals also appeared to be affected, including the microphone. The mouse still worked, and the display was visible, but I could not fully determine the exact extent of the breakage from the broken graphical session alone.
Why I am reporting this generically:
I cannot confidently identify every subsystem that failed. The issue looked broader than a single device failure, so I am reporting it as a kernel regression affecting peripherals / input / general usability rather than only one specific component.
Regression:
Yes. The problem appeared after updating to the HWE 6.17 kernel series, and the system recovered after removing the problematic 6.17 kernels and going back to the stable generic kernel.
Recovery / workaround:
I recovered the machine from an Ubuntu Live USB. I mounted the installed system, entered it through chroot, removed the problematic 6.17 kernel packages, reinstalled the stable generic kernel, regenerated initramfs, and updated GRUB. After reboot, the system started correctly again on 6.8.0-107-generic.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-107-generic 6.8.0-107.107
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
Uname: Linux 6.8.0-107-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: teygeta 2480 F.... wireplumber
/dev/snd/controlC2: teygeta 2480 F.... wireplumber
/dev/snd/controlC0: teygeta 2480 F.... wireplumber
/dev/snd/seq: teygeta 2476 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 5 11:05:30 2026
InstallationDate: Installed on 2026-03-15 (21 days ago)
InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210)
MachineType: MSI MS-7A65
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-ghostty
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-107-generic root=UUID=367ddc98-d2ca-421e-aec3-cebfb331cc7b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-107-generic N/A
linux-backports-modules-6.8.0-107-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M GAMING PRO (MS-7A65)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd07/24/2018:br5.12:svnMSI:pnMS-7A65:pvr1.0:rvnMSI:rnB250MGAMINGPRO(MS-7A65):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A65
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147294/+subscriptions
After updating Ubuntu 24.04 LTS to a recent HWE 6.17 kernel, the system
developed a serious regression after reboot.
What I expected to happen:
The system should boot normally, with working input devices and peripherals, as before the update.
What happened instead:
After reboot, the system became partially unusable. At minimum, the internal keyboard stopped working. Other peripherals also appeared to be affected, including the microphone. The mouse still worked, and the display was visible, but I could not fully determine the exact extent of the breakage from the broken graphical session alone.
Why I am reporting this generically:
I cannot confidently identify every subsystem that failed. The issue looked broader than a single device failure, so I am reporting it as a kernel regression affecting peripherals / input / general usability rather than only one specific component.
Regression:
Yes. The problem appeared after updating to the HWE 6.17 kernel series, and the system recovered after removing the problematic 6.17 kernels and going back to the stable generic kernel.
Recovery / workaround:
I recovered the machine from an Ubuntu Live USB. I mounted the installed system, entered it through chroot, removed the problematic 6.17 kernel packages, reinstalled the stable generic kernel, regenerated initramfs, and updated GRUB. After reboot, the system started correctly again on 6.8.0-107-generic.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-107-generic 6.8.0-107.107
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
Uname: Linux 6.8.0-107-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: teygeta 2480 F.... wireplumber
/dev/snd/controlC2: teygeta 2480 F.... wireplumber
/dev/snd/controlC0: teygeta 2480 F.... wireplumber
/dev/snd/seq: teygeta 2476 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 5 11:05:30 2026
InstallationDate: Installed on 2026-03-15 (21 days ago)
InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210)
MachineType: MSI MS-7A65
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-ghostty
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-107-generic root=UUID=367ddc98-d2ca-421e-aec3-cebfb331cc7b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-107-generic N/A
linux-backports-modules-6.8.0-107-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M GAMING PRO (MS-7A65)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd07/24/2018:br5.12:svnMSI:pnMS-7A65:pvr1.0:rvnMSI:rnB250MGAMINGPRO(MS-7A65):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A65
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug kernel-bug noble wayland-session
** Attachment added: "version.log"
https://bugs.launchpad.net/bugs/2147294/+attachment/5958742/+files/version.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147294
Title:
Regression: Ubuntu 24.04 HWE kernel 6.17 causes multiple device/input
failures after reboot
Status in linux package in Ubuntu:
New
Bug description:
After updating Ubuntu 24.04 LTS to a recent HWE 6.17 kernel, the
system developed a serious regression after reboot.
What I expected to happen:
The system should boot normally, with working input devices and peripherals, as before the update.
What happened instead:
After reboot, the system became partially unusable. At minimum, the internal keyboard stopped working. Other peripherals also appeared to be affected, including the microphone. The mouse still worked, and the display was visible, but I could not fully determine the exact extent of the breakage from the broken graphical session alone.
Why I am reporting this generically:
I cannot confidently identify every subsystem that failed. The issue looked broader than a single device failure, so I am reporting it as a kernel regression affecting peripherals / input / general usability rather than only one specific component.
Regression:
Yes. The problem appeared after updating to the HWE 6.17 kernel series, and the system recovered after removing the problematic 6.17 kernels and going back to the stable generic kernel.
Recovery / workaround:
I recovered the machine from an Ubuntu Live USB. I mounted the installed system, entered it through chroot, removed the problematic 6.17 kernel packages, reinstalled the stable generic kernel, regenerated initramfs, and updated GRUB. After reboot, the system started correctly again on 6.8.0-107-generic.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-107-generic 6.8.0-107.107
ProcVersionSignature: Ubuntu 6.8.0-107.107-generic 6.8.12
Uname: Linux 6.8.0-107-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: teygeta 2480 F.... wireplumber
/dev/snd/controlC2: teygeta 2480 F.... wireplumber
/dev/snd/controlC0: teygeta 2480 F.... wireplumber
/dev/snd/seq: teygeta 2476 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 5 11:05:30 2026
InstallationDate: Installed on 2026-03-15 (21 days ago)
InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210)
MachineType: MSI MS-7A65
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-ghostty
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-107-generic root=UUID=367ddc98-d2ca-421e-aec3-cebfb331cc7b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-107-generic N/A
linux-backports-modules-6.8.0-107-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M GAMING PRO (MS-7A65)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd07/24/2018:br5.12:svnMSI:pnMS-7A65:pvr1.0:rvnMSI:rnB250MGAMINGPRO(MS-7A65):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7A65
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147294/+subscriptions
суббота
[Bug 2062120] Re: lenovo yt3 kernel support
Thank you for sharing the upstream fix.
This fix has already been SRU'd into Ubuntu 24.04 Noble and shipped as of linux-image-6.8.0-86-generic. Please update to the latest kernel. I will set the bug status to "Fix Released". Thank you for your patience and for contributing the upstream fix report.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062120
Title:
lenovo yt3 kernel support
Status in linux package in Ubuntu:
Fix Released
Bug description:
The issue is still present on 6.8.0.31-generic
>>sudo modprobe x86_android_tablets
modprobe: ERROR: could not insert 'x86_android_tablet': No such device
>> dmesg
x86_android_tablets: error -16 getting GPIO INT33FF:01 5
>>sudo modprobe -f x86_android_tablet
modprobe: ERROR: could not insert 'x86_android_tablets': Key was rejected by service
---------------------------------------------------------------------------
on My lenovo yogatab3 the 23.10 ubuntu kernel 6.5.0.27-generic detected and reported the status of the built in batteries.
This is missing for kernel 6.8.0.22-generic
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-22-generic 6.8.0-22.22
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: pipacsba 4730 F.... pulseaudio
CasperMD5json:
{
"result": "skip"
}
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Apr 18 07:09:17 2024
InstallationDate: Installed on 2023-10-14 (187 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 (20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/7p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M
MachineType: Intel Corporation CHERRYVIEW D1 PLATFORM
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-22-generic N/A
linux-backports-modules-6.8.0-22-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-15 (3 days ago)
acpidump:
dmi.bios.date: 01/24/2017
dmi.bios.release: 0.15
dmi.bios.vendor: Intel Corporation
dmi.bios.version: CHTTYOGA.X64.R514.R15.1701241022
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Cherry Trail Tablet
dmi.board.vendor: Intel Corp.
dmi.board.version: 1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnIntelCorporation:bvrCHTTYOGA.X64.R514.R15.1701241022:bd01/24/2017:br0.15:svnIntelCorporation:pnCHERRYVIEWD1PLATFORM:pvrBlade3-10A-001:rvnIntelCorp.:rnCherryTrailTablet:rvr1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber:
dmi.product.family: Cherryview System
dmi.product.name: CHERRYVIEW D1 PLATFORM
dmi.product.sku: System SKUNumber
dmi.product.version: Blade3-10A-001
dmi.sys.vendor: Intel Corporation
mtime.conffile..etc.logrotate.d.apport: 2023-10-15T11:15:11.964957
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062120/+subscriptions
This fix has already been SRU'd into Ubuntu 24.04 Noble and shipped as of linux-image-6.8.0-86-generic. Please update to the latest kernel. I will set the bug status to "Fix Released". Thank you for your patience and for contributing the upstream fix report.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062120
Title:
lenovo yt3 kernel support
Status in linux package in Ubuntu:
Fix Released
Bug description:
The issue is still present on 6.8.0.31-generic
>>sudo modprobe x86_android_tablets
modprobe: ERROR: could not insert 'x86_android_tablet': No such device
>> dmesg
x86_android_tablets: error -16 getting GPIO INT33FF:01 5
>>sudo modprobe -f x86_android_tablet
modprobe: ERROR: could not insert 'x86_android_tablets': Key was rejected by service
---------------------------------------------------------------------------
on My lenovo yogatab3 the 23.10 ubuntu kernel 6.5.0.27-generic detected and reported the status of the built in batteries.
This is missing for kernel 6.8.0.22-generic
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-22-generic 6.8.0-22.22
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: pipacsba 4730 F.... pulseaudio
CasperMD5json:
{
"result": "skip"
}
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Apr 18 07:09:17 2024
InstallationDate: Installed on 2023-10-14 (187 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64 (20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/7p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M
MachineType: Intel Corporation CHERRYVIEW D1 PLATFORM
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-22-generic N/A
linux-backports-modules-6.8.0-22-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-15 (3 days ago)
acpidump:
dmi.bios.date: 01/24/2017
dmi.bios.release: 0.15
dmi.bios.vendor: Intel Corporation
dmi.bios.version: CHTTYOGA.X64.R514.R15.1701241022
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Cherry Trail Tablet
dmi.board.vendor: Intel Corp.
dmi.board.version: 1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnIntelCorporation:bvrCHTTYOGA.X64.R514.R15.1701241022:bd01/24/2017:br0.15:svnIntelCorporation:pnCHERRYVIEWD1PLATFORM:pvrBlade3-10A-001:rvnIntelCorp.:rnCherryTrailTablet:rvr1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber:
dmi.product.family: Cherryview System
dmi.product.name: CHERRYVIEW D1 PLATFORM
dmi.product.sku: System SKUNumber
dmi.product.version: Blade3-10A-001
dmi.sys.vendor: Intel Corporation
mtime.conffile..etc.logrotate.d.apport: 2023-10-15T11:15:11.964957
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062120/+subscriptions
[Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)
Hi, thanks for the detailed logs. The kernel logs show that the
RTL8761BU firmware loads successfully and pairing completes, but the
connection drops immediately afterwards. Another commenter mentioned
that updating the Realtek firmware files resolved the issue for
Could you make sure you have the latest linux-firmware package installed and try again? You can update it with:
sudo apt update && sudo apt install linux-
Then reboot and test the Bluetooth pairing. If the issue persists on the
latest firmware, please let us know your linux-firmware package version
(dpkg -l linux-firmware) and we can investigate further.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062280
Title:
Bluetooth Broken In Kernel Versions 6.5+ (Realtek)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Starting with kernel 6.5 the external Bluetooth USB dongle based on
Realtek stop working.
This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
version is > 6.5. On a lower kernel version it works as we were using
it for almost 2 years without issues.
Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
```
$ uname -a
Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
```
$ lsusb | grep -i bluetooth
Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
```
Journalctl logs after the OS is starting
```
journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
```
I have installed BlueZ package https://www.bluez.org/ and trying to
discover the device which worked but i am always getting errors when
trying to connect to the device via BT (after pairing)
```
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0007
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0007 complete: 0x00
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0006
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0006 complete: 0x00
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00)
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000adb
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000b
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:connected_callback() hci0 device 74:9E:F5:28:3C:4C connected eir_len 15
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000f
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:user_confirm_request_callback() hci0 74:9E:F5:28:3C:4C confirm_hint 0
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/device.c:new_auth() Requesting agent authentication for 74:9E:F5:28:3C:4C
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/agent.c:agent_ref() 0x5e96f8c12780: ref=2
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: name=:1.49, path=/org/bluez/agent, passkey=639324
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_ref() 0x5e96f8c12780: ref=3
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:btd_adapter_confirm_reply() hci0 addr 74:9E:F5:28:3C:4C success 1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_unref() 0x5e96f8c12780: ref=2
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_unref() 0x5e96f8c12780: ref=1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x001c
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x001c complete: 0x00
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0009
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:new_link_key_callback() hci0 new key for 74:9E:F5:28:3C:4C type 5 pin_len 0 store_hint 1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_complete() bonding (nil) status 0x00
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:resume_discovery()
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000c
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:dev_disconnected() Device 74:9E:F5:28:3C:4C disconnected, reason 3
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:adapter_remove_connection()
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: plugins/policy.c:disconnect_cb() reason 3
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 74:9E:F5:28:3C:4C type 0 status 0xe
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_failed() status 14
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:resume_discovery()
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0006
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000ad3
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:set_mode() sending set mode command for index 0
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0007
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0007 complete: 0x00
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0006
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0006 complete: 0x00
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00)
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000adb
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0006
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000ad3
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062280/+subscriptions
RTL8761BU firmware loads successfully and pairing completes, but the
connection drops immediately afterwards. Another commenter mentioned
that updating the Realtek firmware files resolved the issue for
Could you make sure you have the latest linux-firmware package installed and try again? You can update it with:
sudo apt update && sudo apt install linux-
Then reboot and test the Bluetooth pairing. If the issue persists on the
latest firmware, please let us know your linux-firmware package version
(dpkg -l linux-firmware) and we can investigate further.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062280
Title:
Bluetooth Broken In Kernel Versions 6.5+ (Realtek)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Starting with kernel 6.5 the external Bluetooth USB dongle based on
Realtek stop working.
This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
version is > 6.5. On a lower kernel version it works as we were using
it for almost 2 years without issues.
Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
```
$ uname -a
Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
```
$ lsusb | grep -i bluetooth
Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
```
Journalctl logs after the OS is starting
```
journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
```
I have installed BlueZ package https://www.bluez.org/ and trying to
discover the device which worked but i am always getting errors when
trying to connect to the device via BT (after pairing)
```
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0007
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0007 complete: 0x00
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0006
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0006 complete: 0x00
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00)
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000adb
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000b
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:connected_callback() hci0 device 74:9E:F5:28:3C:4C connected eir_len 15
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000f
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:user_confirm_request_callback() hci0 74:9E:F5:28:3C:4C confirm_hint 0
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/device.c:new_auth() Requesting agent authentication for 74:9E:F5:28:3C:4C
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/agent.c:agent_ref() 0x5e96f8c12780: ref=2
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: name=:1.49, path=/org/bluez/agent, passkey=639324
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_ref() 0x5e96f8c12780: ref=3
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:btd_adapter_confirm_reply() hci0 addr 74:9E:F5:28:3C:4C success 1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_unref() 0x5e96f8c12780: ref=2
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/agent.c:agent_unref() 0x5e96f8c12780: ref=1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x001c
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x001c complete: 0x00
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0009
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:new_link_key_callback() hci0 new key for 74:9E:F5:28:3C:4C type 5 pin_len 0 store_hint 1
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_complete() bonding (nil) status 0x00
Apr 18 09:23:14 bomi-edge bluetoothd[2413]: src/adapter.c:resume_discovery()
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000c
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:dev_disconnected() Device 74:9E:F5:28:3C:4C disconnected, reason 3
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:adapter_remove_connection()
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: plugins/policy.c:disconnect_cb() reason 3
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 74:9E:F5:28:3C:4C type 0 status 0xe
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/device.c:device_bonding_failed() status 14
Apr 18 09:23:19 bomi-edge bluetoothd[2413]: src/adapter.c:resume_discovery()
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0006
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000ad3
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:25:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:set_mode() sending set mode command for index 0
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0007
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0007 complete: 0x00
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x0000] command 0x0006
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0006 complete: 0x00
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00)
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000adb
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:29:29 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0006
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x00000ad3
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x00000008
Apr 18 09:32:31 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x00000002
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062280/+subscriptions
[Bug 2059827] Re: System hung indefinitely during a Software Update prompt. The update related to audio. I had to hard restart the system.
Hi, thanks for the report. I've reviewed the attached logs (dmesg, ALSA
info, dependencies) and the kernel boot is clean, there is no hung
tasks, no audio driver errors, and no kernel panics. The HDA Intel audio
and Realtek ALC3204 codec both initialized successfully. This suggests
the hang was likely in userspace (e.g. GNOME Software or the Wayland
compositor) rather than a kernel issue.
Since Ubuntu 23.10 has reached end of life, I'm marking this as
Incomplete. If you're still experiencing this on a supported release
like 24.04, please file a new bug and include the output of apport-
collect so we can investigate further.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2059827
Title:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
Status in linux package in Ubuntu:
Incomplete
Bug description:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: qd91 2577 F.... wireplumber
/dev/snd/seq: qd91 2559 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 30 11:53:18 2024
InstallationDate: Installed on 2024-02-08 (51 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-26-generic N/A
linux-backports-modules-6.5.0-26-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-02-10 (49 days ago)
dmi.bios.date: 11/10/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0772C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
dmi.product.family: Latitude
dmi.product.name: Latitude 5420
dmi.product.sku: 0A20
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059827/+subscriptions
info, dependencies) and the kernel boot is clean, there is no hung
tasks, no audio driver errors, and no kernel panics. The HDA Intel audio
and Realtek ALC3204 codec both initialized successfully. This suggests
the hang was likely in userspace (e.g. GNOME Software or the Wayland
compositor) rather than a kernel issue.
Since Ubuntu 23.10 has reached end of life, I'm marking this as
Incomplete. If you're still experiencing this on a supported release
like 24.04, please file a new bug and include the output of apport-
collect so we can investigate further.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2059827
Title:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
Status in linux package in Ubuntu:
Incomplete
Bug description:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: qd91 2577 F.... wireplumber
/dev/snd/seq: qd91 2559 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 30 11:53:18 2024
InstallationDate: Installed on 2024-02-08 (51 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-26-generic N/A
linux-backports-modules-6.5.0-26-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-02-10 (49 days ago)
dmi.bios.date: 11/10/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0772C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
dmi.product.family: Latitude
dmi.product.name: Latitude 5420
dmi.product.sku: 0A20
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059827/+subscriptions
[Bug 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063077
Title:
Keyboard does not work after waking up from suspend with 5.15.0-105
(but works with 5.15.0-101)
Status in linux package in Ubuntu:
Fix Released
Bug description:
Dear Ubuntu maintainers, I think I found a regression in linux
5.15.0-105.
In the past few days, my keyboard stopped working after waking up from
suspend (sleep), so I couldn't unlock my laptop. Various workarounds
found on the internet helped, but I wanted to investigate if it was a
gdm issue, grub, or a hardware failure. I managed to narrow it down to
the kernel, which is why I'm filing this bug report.
AFAICT the only keys that work are the keyboard lights and the
brightness knobs (in the Fn functions). I can confirm that 5.15.0-105
has the issue, and I can consistently reproduce it with the following
steps:
1. boot fresh with 5.15.0-105
2. login to my account
3. choose suspend from the power menu
4. wake up
Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-105-generic 5.15.0-105.115
ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
Uname: Linux 5.15.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: philsf 5465 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 02:58:26 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc
InstallationDate: Installed on 2018-06-07 (2145 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-105-generic N/A
linux-backports-modules-5.15.0-105-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2023
dmi.bios.release: 1.14
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.name: 0TXW78
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+subscriptions
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2063077
Title:
Keyboard does not work after waking up from suspend with 5.15.0-105
(but works with 5.15.0-101)
Status in linux package in Ubuntu:
Fix Released
Bug description:
Dear Ubuntu maintainers, I think I found a regression in linux
5.15.0-105.
In the past few days, my keyboard stopped working after waking up from
suspend (sleep), so I couldn't unlock my laptop. Various workarounds
found on the internet helped, but I wanted to investigate if it was a
gdm issue, grub, or a hardware failure. I managed to narrow it down to
the kernel, which is why I'm filing this bug report.
AFAICT the only keys that work are the keyboard lights and the
brightness knobs (in the Fn functions). I can confirm that 5.15.0-105
has the issue, and I can consistently reproduce it with the following
steps:
1. boot fresh with 5.15.0-105
2. login to my account
3. choose suspend from the power menu
4. wake up
Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-105-generic 5.15.0-105.115
ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
Uname: Linux 5.15.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: philsf 5465 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 02:58:26 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc
InstallationDate: Installed on 2018-06-07 (2145 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-105-generic N/A
linux-backports-modules-5.15.0-105-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/06/2023
dmi.bios.release: 1.14
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.name: 0TXW78
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+subscriptions
[Bug 2147285] [NEW] 6.19.11
Public bug reported:
If you attempt install using mainline tool, the kernel package fails
install hard and requires forced steps to remove
This shows the error on a 24.04 Xubuntu host that currently has 6.19.10
via the mainline tool, unfortunately the mainline tool lacks force
options and mutes most of the error message of this package install, so
I share it here as is.
sudo dpkg -i linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
Selecting previously unselected package linux-image-unsigned-6.19.11-061911-generic.
(Reading database ... 359250 files and directories currently installed.)
Preparing to unpack linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb ...
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error processing archive linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb (--install):
new linux-image-unsigned-6.19.11-061911-generic package pre-installation script subprocess returned error exit status 1
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error while cleaning up:
new linux-image-unsigned-6.19.11-061911-generic package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
To fix I First:
sudo dpkg --force-all --purge linux-image-unsigned-6.19.11-061911-generic
Then:
sudo apt update && sudo apt full-upgrade && sudo apt autoremove && sudo apt autoclean
You might also have to:
sudo apt remove linux-modules-6.19.11-061911-generic
Also would like to mention thanks for the mainline tool and the ability
to easily get a 6.19.x and such advanced kernel on our AMD and other
modern hardware systems, for testing, and hardware support reasons. Also
thank you to Ubuntu, Linux, and the open source community!! Hope this
helps everyone out, and sorry I am not more of a kernel developer to
help realize why this happened in the first place.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147285
Title:
6.19.11
Status in linux package in Ubuntu:
New
Bug description:
If you attempt install using mainline tool, the kernel package fails
install hard and requires forced steps to remove
This shows the error on a 24.04 Xubuntu host that currently has
6.19.10 via the mainline tool, unfortunately the mainline tool lacks
force options and mutes most of the error message of this package
install, so I share it here as is.
sudo dpkg -i linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
Selecting previously unselected package linux-image-unsigned-6.19.11-061911-generic.
(Reading database ... 359250 files and directories currently installed.)
Preparing to unpack linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb ...
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error processing archive linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb (--install):
new linux-image-unsigned-6.19.11-061911-generic package pre-installation script subprocess returned error exit status 1
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error while cleaning up:
new linux-image-unsigned-6.19.11-061911-generic package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
To fix I First:
sudo dpkg --force-all --purge linux-image-unsigned-6.19.11-061911-generic
Then:
sudo apt update && sudo apt full-upgrade && sudo apt autoremove && sudo apt autoclean
You might also have to:
sudo apt remove linux-modules-6.19.11-061911-generic
Also would like to mention thanks for the mainline tool and the
ability to easily get a 6.19.x and such advanced kernel on our AMD and
other modern hardware systems, for testing, and hardware support
reasons. Also thank you to Ubuntu, Linux, and the open source
community!! Hope this helps everyone out, and sorry I am not more of a
kernel developer to help realize why this happened in the first place.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147285/+subscriptions
If you attempt install using mainline tool, the kernel package fails
install hard and requires forced steps to remove
This shows the error on a 24.04 Xubuntu host that currently has 6.19.10
via the mainline tool, unfortunately the mainline tool lacks force
options and mutes most of the error message of this package install, so
I share it here as is.
sudo dpkg -i linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
Selecting previously unselected package linux-image-unsigned-6.19.11-061911-generic.
(Reading database ... 359250 files and directories currently installed.)
Preparing to unpack linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb ...
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error processing archive linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb (--install):
new linux-image-unsigned-6.19.11-061911-generic package pre-installation script subprocess returned error exit status 1
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error while cleaning up:
new linux-image-unsigned-6.19.11-061911-generic package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
To fix I First:
sudo dpkg --force-all --purge linux-image-unsigned-6.19.11-061911-generic
Then:
sudo apt update && sudo apt full-upgrade && sudo apt autoremove && sudo apt autoclean
You might also have to:
sudo apt remove linux-modules-6.19.11-061911-generic
Also would like to mention thanks for the mainline tool and the ability
to easily get a 6.19.x and such advanced kernel on our AMD and other
modern hardware systems, for testing, and hardware support reasons. Also
thank you to Ubuntu, Linux, and the open source community!! Hope this
helps everyone out, and sorry I am not more of a kernel developer to
help realize why this happened in the first place.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147285
Title:
6.19.11
Status in linux package in Ubuntu:
New
Bug description:
If you attempt install using mainline tool, the kernel package fails
install hard and requires forced steps to remove
This shows the error on a 24.04 Xubuntu host that currently has
6.19.10 via the mainline tool, unfortunately the mainline tool lacks
force options and mutes most of the error message of this package
install, so I share it here as is.
sudo dpkg -i linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
Selecting previously unselected package linux-image-unsigned-6.19.11-061911-generic.
(Reading database ... 359250 files and directories currently installed.)
Preparing to unpack linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb ...
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error processing archive linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb (--install):
new linux-image-unsigned-6.19.11-061911-generic package pre-installation script subprocess returned error exit status 1
run-parts: missing operand
Try `run-parts --help' for more information.
dpkg: error while cleaning up:
new linux-image-unsigned-6.19.11-061911-generic package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-unsigned-6.19.11-061911-generic_6.19.11-061911.202604021147_amd64.deb
To fix I First:
sudo dpkg --force-all --purge linux-image-unsigned-6.19.11-061911-generic
Then:
sudo apt update && sudo apt full-upgrade && sudo apt autoremove && sudo apt autoclean
You might also have to:
sudo apt remove linux-modules-6.19.11-061911-generic
Also would like to mention thanks for the mainline tool and the
ability to easily get a 6.19.x and such advanced kernel on our AMD and
other modern hardware systems, for testing, and hardware support
reasons. Also thank you to Ubuntu, Linux, and the open source
community!! Hope this helps everyone out, and sorry I am not more of a
kernel developer to help realize why this happened in the first place.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147285/+subscriptions
[Bug 2147246] Re: USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic (works on 6.17.0-19)
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147246
Title:
USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic
(works on 6.17.0-19)
Status in linux package in Ubuntu:
New
Bug description:
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147246/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147246
Title:
USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic
(works on 6.17.0-19)
Status in linux package in Ubuntu:
New
Bug description:
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147246/+subscriptions
[Bug 2147249] Re: System randomly suspends
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147249
Title:
System randomly suspends
Status in linux package in Ubuntu:
New
Bug description:
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147249/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147249
Title:
System randomly suspends
Status in linux package in Ubuntu:
New
Bug description:
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147249/+subscriptions
[Bug 2147274] Re: Regression: Framework audio expansion card fails after AC to battery transition (6.17.0-20)
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
Подписаться на:
Комментарии (Atom)