Public bug reported: The audio card of my Asus UM5606GA is not recognized by Ubuntu 26.04 (only a "dummy device"). $ cat /proc/version Linux version 7.0.0-27-generic (buildd@lcy02-amd64-114) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #27-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun 18 19:13:49 UTC 2026 Installing Linux 7.1-rc5 or higher fixes the problem. I believe this is the relevant commit (but I did not test that it is the _only_ commit needed): https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=6e4bfd9da885 Please backport support to the Ubuntu kernel. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: crusaderky 2909 F.... wireplumber /dev/snd/seq: crusaderky 2889 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 16:03:18 2026 InstallationDate: Installed on 2026-07-10 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS Zenbook S16 UM5606GA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash nomodeset crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5606GA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5606GA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5606GA.305:bd02/25/2026:br5.35:efr3.3:svnASUS:pnZenbookS16UM5606GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5606GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenbookS16: dmi.product.family: Zenbook S16 dmi.product.name: Zenbook S16 UM5606GA dmi.product.version: 1.0 dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160342 Title: Asus Zenbook UM5606GA: no audio Status in linux package in Ubuntu: New Bug description: The audio card of my Asus UM5606GA is not recognized by Ubuntu 26.04 (only a "dummy device"). $ cat /proc/version Linux version 7.0.0-27-generic (buildd@lcy02-amd64-114) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #27-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun 18 19:13:49 UTC 2026 Installing Linux 7.1-rc5 or higher fixes the problem. I believe this is the relevant commit (but I did not test that it is the _only_ commit needed): https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=6e4bfd9da885 Please backport support to the Ubuntu kernel. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: crusaderky 2909 F.... wireplumber /dev/snd/seq: crusaderky 2889 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 16:03:18 2026 InstallationDate: Installed on 2026-07-10 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS Zenbook S16 UM5606GA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash nomodeset crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5606GA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5606GA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5606GA.305:bd02/25/2026:br5.35:efr3.3:svnASUS:pnZenbookS16UM5606GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5606GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenbookS16: dmi.product.family: Zenbook S16 dmi.product.name: Zenbook S16 UM5606GA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160342/+subscriptions
пятница
[Bug 2160302] Re: Drop DEP-8 tests from kernel packages
** Changed in: linux (Ubuntu Stonking) Status: Triaged => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160302 Title: Drop DEP-8 tests from kernel packages Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Triaged Status in linux source package in Noble: Triaged Status in linux source package in Resolute: Triaged Status in linux source package in Stonking: In Progress Bug description: == SRU Justification == Impact: We added DEP-8 tests to the kernel package when there was no other testing. Today we do much more thorough regression testing internally (RT is a superset of kernel ADT). Given that generally ADT is already struggling to cope and we literally get no added value from running the same tests in ADT and RT lets drop the tests from ADT. This does not change the fact that the tests of other packages with relations to the kernel get run in ADT for each new kernel (DKMS, snapd, systemd, glibc, ...). Fix: Delete debian/tests from the kernel source package. Testcase: The kernel package stops showing as separate test run on ADT. Other packages get still triggered for new kernel uploads. Regression Potential: Possibly the missing test gets flagged on the first modified upload and has to be accepted. Otherwise nothing should hard rely on those tests to be run in ADT. And they still run for RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160302/+subscriptions
[Bug 2159600] Re: Kernel panic interrupt
Reformatted partition and reinstalled Ubuntu 26.04, problem solved (apparently!) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159600 Title: Kernel panic interrupt Status in linux package in Ubuntu: New Bug description: The computer has stopped with a kernel panic reporting something about an interrupt Description: Ubuntu 26.04 LTS Release: 26.04 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: lan 4629 F.... wireplumber /dev/snd/seq: lan 4612 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 21:04:25 2026 InstallationDate: Installed on 2021-07-07 (1824 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 13d3:5415 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: LENOVO 20R4S3FX00 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=942c846d-810e-4a08-85a2-d47c9582cedf ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-18 (48 days ago) dmi.bios.date: 07/13/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R15ET54W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R4S3FX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR15ET54W(1.35):bd07/13/2022:br1.35:efr1.12:svnLENOVO:pn20R4S3FX00:pvrThinkPadL13Gen1:rvnLENOVO:rn20R4S3FX00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R4_BU_Think_FM_ThinkPadL13Gen1:pfaThinkPadL13Gen1: dmi.product.family: ThinkPad L13 Gen 1 dmi.product.name: 20R4S3FX00 dmi.product.sku: LENOVO_MT_20R4_BU_Think_FM_ThinkPad L13 Gen 1 dmi.product.version: ThinkPad L13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159600/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-ibm/6.8.0-1061.62)
All autopkgtests for the newly accepted linux-meta-ibm (6.8.0-1061.62) for noble have finished running. The following regressions have been reported in tests triggered by the package: dkms/3.0.11-1ubuntu13 (amd64) dpdk-kmods/0~20230205+git-1 (amd64) glibc/2.39-0ubuntu8.7 (amd64) linux-ibm/6.8.0-1061.62 (amd64) lxc/unknown (amd64) zfs-linux/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta-ibm [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2160302] [NEW] Drop DEP-8 tests from kernel packages
Public bug reported: == SRU Justification == Impact: We added DEP-8 tests to the kernel package when there was no other testing. Today we do much more thorough regression testing internally (RT is a superset of kernel ADT). Given that generally ADT is already struggling to cope and we literally get no added value from running the same tests in ADT and RT lets drop the tests from ADT. This does not change the fact that the tests of other packages with relations to the kernel get run in ADT for each new kernel (DKMS, snapd, systemd, glibc, ...). Fix: Delete debian/tests from the kernel source package. Testcase: The kernel package stops showing as separate test run on ADT. Other packages get still triggered for new kernel uploads. Regression Potential: Possibly the missing test gets flagged on the first modified upload and has to be accepted. Otherwise nothing should hard rely on those tests to be run in ADT. And they still run for RT. ** Affects: linux (Ubuntu) Importance: Low Assignee: Stefan Bader (smb) Status: Triaged ** Affects: linux (Ubuntu Jammy) Importance: Low Status: Triaged ** Affects: linux (Ubuntu Noble) Importance: Low Status: Triaged ** Affects: linux (Ubuntu Resolute) Importance: Low Status: Triaged ** Affects: linux (Ubuntu Stonking) Importance: Low Assignee: Stefan Bader (smb) Status: Triaged ** Also affects: linux (Ubuntu Stonking) Importance: Low Assignee: Stefan Bader (smb) Status: Triaged ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Resolute) Status: New => Triaged ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Low ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160302 Title: Drop DEP-8 tests from kernel packages Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Noble: Triaged Status in linux source package in Resolute: Triaged Status in linux source package in Stonking: Triaged Bug description: == SRU Justification == Impact: We added DEP-8 tests to the kernel package when there was no other testing. Today we do much more thorough regression testing internally (RT is a superset of kernel ADT). Given that generally ADT is already struggling to cope and we literally get no added value from running the same tests in ADT and RT lets drop the tests from ADT. This does not change the fact that the tests of other packages with relations to the kernel get run in ADT for each new kernel (DKMS, snapd, systemd, glibc, ...). Fix: Delete debian/tests from the kernel source package. Testcase: The kernel package stops showing as separate test run on ADT. Other packages get still triggered for new kernel uploads. Regression Potential: Possibly the missing test gets flagged on the first modified upload and has to be accepted. Otherwise nothing should hard rely on those tests to be run in ADT. And they still run for RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160302/+subscriptions
[Bug 2160286] [NEW] CAN-J1939: sendmsg control data is not used
Public bug reported: Some protocols based on J1939 require PGNs be sent with different priorities. Although the priority can be set using setsockopt(2) with the SO_J1939_SEND_PRIO socket option, this requires two system calls to send a message leading to a potential race condition if the socket is shared between threads. The sendmsg(2) call allows socket options to be supplied as ancillary control data as part of a single send operation. However, it appears the J1939 driver does not process these options and messages are always transmitted with the priority set at the socket level. https://github.com/torvalds/linux/blob/a635d6748234582ea287c5ffeae28b9b23f91c7e/net/can/j1939/socket.c#L919 Ideally, sendmsg should allow any transmit-side socket options (e.g. SO_J1939_SEND_PRIO, SO_BROADCAST) to be supplied on a per-send basis. Attached is a simple C program to reproduce. the second sendmsg transmits with the default priority as observed in candump output: vcan0 1BFFFF42 [5] 48 65 6C 6C 6F vcan0 1BFFFF42 [5] 48 65 6C 6C 6F ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jeremy 2469 F.... wireplumber /dev/snd/seq: jeremy 2448 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 07:54:52 2026 InstallationDate: Installed on 2026-06-28 (12 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 258a:0010 Hailuck Co.,Ltd PTP TouchPad Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 004: ID 0e8d:7961 MediaTek Inc. Wireless_Device Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro Computer(HK) Tech Limited Venus series 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=/boot/vmlinuz-7.0.0-27-generic root=UUID=cb056be5-6cde-4da3-a5c5-3cadf16217a7 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.01 dmi.board.asset.tag: Default string dmi.board.name: AHBTB dmi.board.vendor: Shenzhen Meigao Electronic Equipment Co.,Ltd dmi.board.version: OEM dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.01:bd08/10/2023:br5.25:svnMicroComputer(HK)TechLimited:pnVenusseries:pvrOEM:rvnShenzhenMeigaoElectronicEquipmentCo.,Ltd:rnAHBTB:rvrOEM:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: Venus series dmi.product.sku: Default string dmi.product.version: OEM dmi.sys.vendor: Micro Computer(HK) Tech Limited ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "Reproduction" https://bugs.launchpad.net/bugs/2160286/+attachment/5980981/+files/main.c -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160286 Title: CAN-J1939: sendmsg control data is not used Status in linux package in Ubuntu: New Bug description: Some protocols based on J1939 require PGNs be sent with different priorities. Although the priority can be set using setsockopt(2) with the SO_J1939_SEND_PRIO socket option, this requires two system calls to send a message leading to a potential race condition if the socket is shared between threads. The sendmsg(2) call allows socket options to be supplied as ancillary control data as part of a single send operation. However, it appears the J1939 driver does not process these options and messages are always transmitted with the priority set at the socket level. https://github.com/torvalds/linux/blob/a635d6748234582ea287c5ffeae28b9b23f91c7e/net/can/j1939/socket.c#L919 Ideally, sendmsg should allow any transmit-side socket options (e.g. SO_J1939_SEND_PRIO, SO_BROADCAST) to be supplied on a per-send basis. Attached is a simple C program to reproduce. the second sendmsg transmits with the default priority as observed in candump output: vcan0 1BFFFF42 [5] 48 65 6C 6C 6F vcan0 1BFFFF42 [5] 48 65 6C 6C 6F ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jeremy 2469 F.... wireplumber /dev/snd/seq: jeremy 2448 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 07:54:52 2026 InstallationDate: Installed on 2026-06-28 (12 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 258a:0010 Hailuck Co.,Ltd PTP TouchPad Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 004: ID 0e8d:7961 MediaTek Inc. Wireless_Device Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro Computer(HK) Tech Limited Venus series 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=/boot/vmlinuz-7.0.0-27-generic root=UUID=cb056be5-6cde-4da3-a5c5-3cadf16217a7 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.01 dmi.board.asset.tag: Default string dmi.board.name: AHBTB dmi.board.vendor: Shenzhen Meigao Electronic Equipment Co.,Ltd dmi.board.version: OEM dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.01:bd08/10/2023:br5.25:svnMicroComputer(HK)TechLimited:pnVenusseries:pvrOEM:rvnShenzhenMeigaoElectronicEquipmentCo.,Ltd:rnAHBTB:rvrOEM:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: Venus series dmi.product.sku: Default string dmi.product.version: OEM dmi.sys.vendor: Micro Computer(HK) Tech Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160286/+subscriptions
четверг
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-fde-6.8/6.8.0-1062.69~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-fde-6.8 (6.8.0-1062.69~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure- fde-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia/5.15.0.1107.107)
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1107.107) for jammy have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/1.2.2-1 (amd64) adv-17v35x/5.0.6.0-1ubuntu1 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu10~22.04.1 (amd64) broadcom-sta/6.30.223.271-23~22.04.1 (amd64) ddcci-driver-linux/0.4.1-3ubuntu4 (amd64) digimend-dkms/10-4ubuntu0.1 (amd64) dm-writeboost/2.2.13-1ubuntu4 (amd64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64) evdi/unknown (amd64) glibc/2.35-0ubuntu3.13 (amd64) gost-crypto/0.3.3-1ubuntu2 (amd64) iptables-netflow/2.6-2ubuntu4 (amd64) ipu6-drivers/0~git202211220708.278b7e3d-0ubuntu0.22.04.1 (amd64) ivsc-driver/0~git202211241536.70d95269-0ubuntu0.22.04.2 (amd64) jool/4.1.7-1ubuntu2 (amd64) langford/0.0.20130228-6.1 (amd64) librem-ec-acpi/0.9.1-2ubuntu3 (amd64) libvpoll-eventfd/0.1-2ubuntu2 (amd64) linux-apfs-rw/0.3.2-0ubuntu5~22.04.1 (amd64) linux-nvidia/5.15.0-1107.108 (amd64) lttng-modules/2.13.11-1ubuntu1~22.04.2 (amd64) lxc/1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1 (amd64) nat-rtsp/0.7+5.3-0.1ubuntu1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64) nvidia-graphics-drivers-418-server/418.226.00-0ubuntu5~0.22.04.1 (amd64) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) openafs/1.8.10-2ubuntu1~22.04.2 (amd64) openrazer/3.2.0+dfsg-3 (amd64) oss4/4.2-build2010-5ubuntu9.1 (amd64) r8125/9.007.01-3ubuntu0.3 (amd64) r8168/8.049.02-1ubuntu1.4 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.2 (amd64) rtl8821ce/5.5.2.1-0ubuntu11~0.22.04.1 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) sysdig/0.27.1-0.3ubuntu0.5 (amd64) tp-smapi/0.43-1ubuntu1 (amd64) west-chamber/20100405+svn20111107.r124-14 (amd64) xtables-addons/3.19-1ubuntu1 (amd64) xtrx-dkms/0.0.1+git20190320.5ae3a3e-3ubuntu1~22.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1107.108)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1107.108) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, armhf, i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-nvidia [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2160205] Re: [26.10 FEAT] [SEC2560] openCryptoki CCA token: support PKCS #11 V3.2 ML-DSA
** Package changed: linux (Ubuntu) => opencryptoki (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: opencryptoki (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160205 Title: [26.10 FEAT] [SEC2560] openCryptoki CCA token: support PKCS #11 V3.2 ML-DSA Status in Ubuntu on IBM z Systems: New Status in opencryptoki package in Ubuntu: New Bug description: PKCS #11 v3.2 introduces mechanisms for ML-DSA. CCA token support for these mechanisms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2160205/+subscriptions
[Bug 2160200] [NEW] Fix no audio input/output device on Dell WCLSlate platform with CirrusLogic audio solution
Public bug reported: [Impact] Dell Slate WCL platform with CirrusLogic audio solution fail to register audio input/output device. [Fix] Fix the backport commits for IPC4 and SDCA functions from upstream [Test Case] 1. Boot up the machine of new Dell Slate WCL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound 3. Make sure the output and input device are not Dummy 4. Make sure audio input/output function works OK. [Where problems could occur] The new SDCA and IPC4 function needs to be backported for the Intel WCL platform. The risk of regression has to be addressed on Intel WCL platforms ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160200 Title: Fix no audio input/output device on Dell WCLSlate platform with CirrusLogic audio solution Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Dell Slate WCL platform with CirrusLogic audio solution fail to register audio input/output device. [Fix] Fix the backport commits for IPC4 and SDCA functions from upstream [Test Case] 1. Boot up the machine of new Dell Slate WCL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound 3. Make sure the output and input device are not Dummy 4. Make sure audio input/output function works OK. [Where problems could occur] The new SDCA and IPC4 function needs to be backported for the Intel WCL platform. The risk of regression has to be addressed on Intel WCL platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160200/+subscriptions
[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages
To address the second half of the bug report, it seems that boot- managed-by-snapd should conflict with all linux-firmware-* packages or have some other mechanism to prevent users from inadvertently breaking their system, similarly to LP: #2096979 and LP: #2157702. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in canonical-kernel-snaps: Confirmed Status in boot-managed-by-snapd package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-intel-wireless package in Ubuntu: Invalid Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2150769/+subscriptions
[Bug 2150769] Re: There is a conflict between the pc-kernel snap and additional firmware packages
** Also affects: boot-managed-by-snapd (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/2150769 Title: There is a conflict between the pc-kernel snap and additional firmware packages Status in canonical-kernel-snaps: Confirmed Status in boot-managed-by-snapd package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-intel-wireless package in Ubuntu: Invalid Bug description: I described in detail here, in case I miss anything in this description: https://discourse.ubuntu.com/t/the-pc-kernel-snap- on-26-04-prevents-users-from-installing-additional-firmware/81404 This bug report is pretty wordy so here's a top-line summary: 1. The pc-kernel snap uses an unfortunately unreliable method of including firmware, which means some firmware gets missed 2. The apt dependencies of `boot-managed-by-snapd` preclude installing `linux-firmware` but do not preclude installing any other firmware packages making it possible to break your system in a pretty dramatic way that many users might have a very difficult time figuring out or resolving. Reproduction steps: 1. Install Ubuntu using the `pc-kernel` snap rather than apt kernel packages 2. Install the `linux-firmware-intel-wireless` package Okay, now on to the verbose part of the bug report which I hope is at least partially understandable. Circumstance: 1. I'm running Ubuntu 26.04 using the pc-kernel snapo (because of hardware FDE I guess) 2. My laptop has a pretty new Arrow Lake chipset with an Intel wifi adapter 3. My wifi doesn't work What I discovered while debugging: the `iwlwifi` module won't load properly because it can't find the firmware file it wants, as it is not present in the `pc-kernel` snap, so wifi doesn't work. This took me in a few different directions and this is what I found: * Unspecified incompatibility between pc-kernel and additional firmware packages First, the pc-kernel snap creates symlinks to everything in its 'firmware' directory into the filesystem that gets mounted at /usr/lib/firmware, but it links everything at the top-level. That means firmware can be added to e.g. /usr/lib/firmware/somefile.fw, because that's a directory, but not /usr/lib/firmware/intel/somefile.fw because /usr/lib/firmware/intel is a symlink to a directory on the squashfs filesystem. This means that installing the `linux-firmware-intel-wireless` package, which has the firmware I need: 1. Breaks when trying to install because it tries to write some files to /usr/lib/firmware/intel/ 2. Refuses to uninstall until it's installed correctly, because dpkg recognizes it as being in an extremely broken state. I say 'unspecified' because `boot-managed-by-snapd` explicitly conflicts with `linux-firmware` (showing the intention to not allow both at once), but it does not conflict with any additional firmware packages. * Incomplete firmware inventory in the pc-kernel snap I dug into it a bit and found that the pc-kernel snap builds using the following steps: 1. Get the kernel and the modules together 2. Ask each module what firmware it wants (via `modinfo`) 3. Bundle those firmwares into the pc-kernel snap Unfortunately, for whatever reason, the `iwlwifi` firmware does not specify the firmware that my system seems to insist on, which is `bz-b0-fm-c0-c101.ucode`, so it does not get included into the pc- kernel snap. The `linux-firmware-intel-wireless` debian package *does* include this firmware, presumably because it just includes all available Intel wireless firmware unconditionally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dan 6392 F.... wireplumber /dev/snd/controlC1: dan 6392 F.... wireplumber /dev/snd/controlC0: dan 6392 F.... wireplumber /dev/snd/seq: dan 6354 F.... pipewire CasperMD5CheckMismatches: ./EFI/boot/bootx64.efi ./EFI/boot/grubx64.efi ./EFI/boot/mmx64.efi CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 10:29:41 2026 MachineType: Dell Inc. Dell Pro Max 14 Premium MA14250 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,," RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2025 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06XRHN dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/11/2025:br1.7:efr1.6:svnDellInc.:pnDellProMax14PremiumMA14250:pvr:rvnDellInc.:rn06XRHN:rvrA02:cvnDellInc.:ct10:cvr:sku0D32:pfaDellProMaxLaptops: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 Premium MA14250 dmi.product.sku: 0D32 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2150769/+subscriptions