[Bug 2150819] [NEW] Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install.

Public bug reported: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install. This appears related to Ubuntu bug #2107320: https://bugs.launchpad.net/bugs/2107320 That bug added support for the Sony IMX471 / SONY471A camera sensor on Intel IPU7 platforms. My system detects the same SONY471A sensor, but the IPU7 bridge fails with a duplicate software node error before camera/media devices are created. System: - Lenovo 21Q7000LBR - Ubuntu 26.04 LTS - Kernel: 7.0.0-15-generic - intel-ipu7-dkms: 0~git202602091007.a88b1909-0ubuntu1 - Sensor appears to be Sony IMX471 / SONY471A - BIOS IntegratedCameraAccess: Enable Problem: - No /dev/video* devices are created - No /dev/media* devices are created - Camera apps cannot see the internal webcam Relevant kernel log: Found supported sensor SONY471A:00 sysfs: cannot create duplicate filename '/kernel/software_nodes/SONY471A-0' kobject: kobject_add_internal failed for SONY471A-0 with -EEXIST intel-ipu7 0000:00:05.0: error -EEXIST: IPU bridge init failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -17 Expected behavior: The IPU7 driver should bind the IMX471 sensor and create camera/media devices, similar to the expected working path from Ubuntu bug #2107320: Found supported sensor SONY471A:00 Connected 1 cameras bind imx471 ... All sensor registration completed ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: portugal 3618 F.... pipewire portugal 3640 F.... wireplumber /dev/snd/seq: portugal 3618 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:18:01 2026 InstallationDate: Installed on 2026-05-02 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21Q7000LBR ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=57b10f72-ea94-4402-b27e-a35bf6019678 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux StagingDrivers: intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2025 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N4CET36W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21Q7000LBR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN4CET36W(1.12):bd03/06/2025:br1.12:efr1.8:svnLENOVO:pn21Q7000LBR:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7000LBR:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:pfaThinkPadX9-15Gen1: dmi.product.family: ThinkPad X9-15 Gen 1 dmi.product.name: 21Q7000LBR dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1 dmi.product.version: ThinkPad X9-15 Gen 1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute staging -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150819 Title: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install. Status in linux package in Ubuntu: New Bug description: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install. This appears related to Ubuntu bug #2107320: https://bugs.launchpad.net/bugs/2107320 That bug added support for the Sony IMX471 / SONY471A camera sensor on Intel IPU7 platforms. My system detects the same SONY471A sensor, but the IPU7 bridge fails with a duplicate software node error before camera/media devices are created. System: - Lenovo 21Q7000LBR - Ubuntu 26.04 LTS - Kernel: 7.0.0-15-generic - intel-ipu7-dkms: 0~git202602091007.a88b1909-0ubuntu1 - Sensor appears to be Sony IMX471 / SONY471A - BIOS IntegratedCameraAccess: Enable Problem: - No /dev/video* devices are created - No /dev/media* devices are created - Camera apps cannot see the internal webcam Relevant kernel log: Found supported sensor SONY471A:00 sysfs: cannot create duplicate filename '/kernel/software_nodes/SONY471A-0' kobject: kobject_add_internal failed for SONY471A-0 with -EEXIST intel-ipu7 0000:00:05.0: error -EEXIST: IPU bridge init failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -17 Expected behavior: The IPU7 driver should bind the IMX471 sensor and create camera/media devices, similar to the expected working path from Ubuntu bug #2107320: Found supported sensor SONY471A:00 Connected 1 cameras bind imx471 ... All sensor registration completed ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: portugal 3618 F.... pipewire portugal 3640 F.... wireplumber /dev/snd/seq: portugal 3618 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:18:01 2026 InstallationDate: Installed on 2026-05-02 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21Q7000LBR ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=57b10f72-ea94-4402-b27e-a35bf6019678 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux StagingDrivers: intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2025 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N4CET36W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21Q7000LBR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN4CET36W(1.12):bd03/06/2025:br1.12:efr1.8:svnLENOVO:pn21Q7000LBR:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7000LBR:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:pfaThinkPadX9-15Gen1: dmi.product.family: ThinkPad X9-15 Gen 1 dmi.product.name: 21Q7000LBR dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1 dmi.product.version: ThinkPad X9-15 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150819/+subscriptions

[Bug 2067498] Re: Can't control display backlight in 24.04 on Dell AIO system

Well the brightness slider is here and working for me with 24.04.04 Fresh install, kernel is Linux 6.17.0-23-generic x86_64 (uname -smr) It now works out of the box with 24.04.04, but not with 26.04. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2067498 Title: Can't control display backlight in 24.04 on Dell AIO system Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 23.10/24.04 Dell Inspiron 7700 AIO 6.5.0-35-generic/6.8.0-31-generic X11 https://askubuntu.com/questions/1514988/backlight-brightness-not- working-in-ubuntu-23-10-24-04-on-dell-7700-aio lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 dell-uart-backlight kernel driver isn't in the 24.04 distribution, so NO Dell AIO display backlights can be adjusted. No brightness slider appears. (dell-uart-backlight is in the 23.10 distribution, but backlight/brightness slider control doesn't work 100% properly). Works fine in 23.04. ls -alR /lib/modules/6.5.0-35-generic/ | grep dell -rw-r--r-- 1 root root 13689 Apr 26 02:32 dell-smm-hwmon.ko.zst drwxr-xr-x 3 root root 4096 May 15 19:10 dell /lib/modules/6.5.0-35-generic/kernel/drivers/platform/x86/dell: -rw-r--r-- 1 root root 18647 Apr 26 02:32 dell-laptop.ko.zst -rw-r--r-- 1 root root 6158 Apr 26 02:32 dell-rbtn.ko.zst -rw-r--r-- 1 root root 8431 Apr 26 02:32 dell_rbu.ko.zst -rw-r--r-- 1 root root 13963 Apr 26 02:32 dell-smbios.ko.zst -rw-r--r-- 1 root root 4432 Apr 26 02:32 dell-smo8800.ko.zst -rw-r--r-- 1 root root 7762 Apr 26 02:32 dell-uart-backlight.ko.zst -rw-r--r-- 1 root root 3799 Apr 26 02:32 dell-wmi-aio.ko.zst -rw-r--r-- 1 root root 9209 Apr 26 02:32 dell-wmi-ddv.ko.zst -rw-r--r-- 1 root root 4532 Apr 26 02:32 dell-wmi-descriptor.ko.zst -rw-r--r-- 1 root root 11198 Apr 26 02:32 dell-wmi.ko.zst -rw-r--r-- 1 root root 3115 Apr 26 02:32 dell-wmi-led.ko.zst drwxr-xr-x 2 root root 4096 May 15 19:10 dell-wmi-sysman /lib/modules/6.5.0-35-generic/kernel/drivers/platform/x86/dell/dell-wmi-sysman: -rw-r--r-- 1 root root 18312 Apr 26 02:32 dell-wmi-sysman.ko.zst ls -alR /lib/modules/6.8.0-31-generic/ | grep dell -rw-r--r-- 1 root root 15140 Apr 19 14:46 dell-smm-hwmon.ko.zst drwxr-xr-x 3 root root 4096 May 25 10:15 dell /lib/modules/6.8.0-31-generic/kernel/drivers/platform/x86/dell: -rw-r--r-- 1 root root 18629 Apr 19 14:46 dell-laptop.ko.zst -rw-r--r-- 1 root root 6180 Apr 19 14:46 dell-rbtn.ko.zst -rw-r--r-- 1 root root 8582 Apr 19 14:46 dell_rbu.ko.zst -rw-r--r-- 1 root root 14726 Apr 19 14:46 dell-smbios.ko.zst -rw-r--r-- 1 root root 4433 Apr 19 14:46 dell-smo8800.ko.zst -rw-r--r-- 1 root root 3790 Apr 19 14:46 dell-wmi-aio.ko.zst -rw-r--r-- 1 root root 9166 Apr 19 14:46 dell-wmi-ddv.ko.zst -rw-r--r-- 1 root root 4492 Apr 19 14:46 dell-wmi-descriptor.ko.zst -rw-r--r-- 1 root root 11306 Apr 19 14:46 dell-wmi.ko.zst -rw-r--r-- 1 root root 3108 Apr 19 14:46 dell-wmi-led.ko.zst drwxr-xr-x 2 root root 4096 May 25 10:15 dell-wmi-sysman /lib/modules/6.8.0-31-generic/kernel/drivers/platform/x86/dell/dell-wmi-sysman: -rw-r--r-- 1 root root 18307 Apr 19 14:46 dell-wmi-sysman.ko.zst dup: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067497 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/seq: al 3689 F.... pipewire  /dev/snd/controlC1: al 3696 F.... wireplumber  /dev/snd/controlC0: al 3696 F.... wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 29 08:32:16 2024 InstallationDate: Installed on 2021-09-25 (978 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 7700 AIO 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-6.8.0-31-generic root=UUID=f0db2226-e28d-46dd-9b5a-457c87987ed2 ro quiet splash ipv6.disable=1 acpi_backlight=vendor acpi_osi=Linux vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.8.0-31-generic N/A  linux-backports-modules-6.8.0-31-generic N/A  linux-firmware 20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-05-25 (4 days ago) dmi.bios.date: 03/27/2024 dmi.bios.release: 1.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 0K9T56 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd03/27/2024:br1.28:svnDellInc.:pnInspiron7700AIO:pvr:rvnDellInc.:rn0K9T56:rvrA00:cvnDellInc.:ct13:cvr:sku0A07: dmi.product.family: Inspiron dmi.product.name: Inspiron 7700 AIO dmi.product.sku: 0A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067498/+subscriptions

[Bug 2146485] Re: IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops at i8042 kernel driver level

Ok, thank you for sharing, I'll try with AI, maybe it will help. However, the problem seems to be very common on these laptop. In this article, a lot of people report the same issue on the same laptop : https://www.reddit.com/r/Lenovo/comments/1qgzkby/consumer_warning_lenovo_ideapad_slim_5_14akp10/ -- 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 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.15.0-1104.110)

All autopkgtests for the newly accepted linux-restricted-modules-oracle (5.15.0-1104.110) 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 (armhf) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-525-server/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/jammy/update_excuses.html#linux-restricted-modules-oracle [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-1102.103)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1102.103) 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 (armhf) nvidia-graphics-drivers-450-server/unknown (amd64) nvidia-graphics-drivers-525-server/525.147.05-0ubuntu2.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 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1107.114)

All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1107.114) 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 (armhf) nvidia-graphics-drivers-390/unknown (amd64) nvidia-graphics-drivers-450-server/unknown (amd64) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/unknown (amd64) nvidia-graphics-drivers-525/unknown (amd64) nvidia-graphics-drivers-525-server/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/jammy/update_excuses.html#linux-restricted-modules-aws [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-1102.103)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia (5.15.0-1102.103) 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 (armhf) nvidia-graphics-drivers-450-server/unknown (amd64) nvidia-graphics-drivers-525-server/525.147.05-0ubuntu2.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 2150795] [NEW] USB HID device not detected on kernel 6.17 (works on 6.8)

Public bug reported: System: Linux Mint (Ubuntu-based), XFCE Kernel (broken): 6.17.0-23-generic Kernel (working): 6.8.0-111-generic Hardware: - AMD Ryzen 7 9800X3D - NVIDIA GPU - USB rudder pedals (HID device) Problem: The rudder pedals are not detected at all when using kernel 6.17. Symptoms: - Device not present in /dev/input - Not visible in evtest or jstest-gtk - Applications (e.g., X-Plane 12) cannot detect it Working condition: - Booting into kernel 6.8 → device works immediately and fully Conclusion: Regression in kernel 6.17 affecting USB HID input device detection. ** 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/2150795 Title: USB HID device not detected on kernel 6.17 (works on 6.8) Status in linux package in Ubuntu: New Bug description: System: Linux Mint (Ubuntu-based), XFCE Kernel (broken): 6.17.0-23-generic Kernel (working): 6.8.0-111-generic Hardware: - AMD Ryzen 7 9800X3D - NVIDIA GPU - USB rudder pedals (HID device) Problem: The rudder pedals are not detected at all when using kernel 6.17. Symptoms: - Device not present in /dev/input - Not visible in evtest or jstest-gtk - Applications (e.g., X-Plane 12) cannot detect it Working condition: - Booting into kernel 6.8 → device works immediately and fully Conclusion: Regression in kernel 6.17 affecting USB HID input device detection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150795/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.15.0-1104.110)

All autopkgtests for the newly accepted linux-restricted-modules-oracle (5.15.0-1104.110) 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 (armhf) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-525-server/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/jammy/update_excuses.html#linux-restricted-modules-oracle [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 2150737] [NEW] M3800 keyboard backlight problem ubuntu 26.04

Public bug reported: Hi, I have a bug related to the keyboard backlight of my DELL M3800. If I use FN + F10 key combinaison all is working good. If I try to use the gnome setting or kde setting, nothing happens. rom1@rom1-M3800:~$ ls /sys/class/leds dell::kbd_backlight input3::capslock input3::numlock input3::scrolllock phy0-led rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/brightness 0 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/max_brightness 2 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/trigger [none] usb-gadget usb-host rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 panic ACAD-online BAT1-charging-or-full BAT1-charging BAT1-full BAT1-charging-blink-full-solid BAT1-charging-orange-full-green mmc0 rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio rfkill2 If I use the key combinaison I can see the value of brightness move from 0 to 2 or 1 and physically the keyboard backlight works well. If I try to force the value to 2 in the brightness using command line, nothing happens and the value foes back to 0. I tried with Ubuntu 26.04, Kubuntu 26.04 and Fedora 44 gnome + kde. All have the same behaviour. Could you please fix this ? Best regards. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: rom1 3768 F.... wireplumber /dev/snd/controlC0: rom1 3768 F.... wireplumber /dev/snd/seq: rom1 3749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 13:07:07 2026 InstallationDate: Installed on 2026-04-24 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Dell Precision M3800 ProcEnviron: LANG=fr_FR.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-15-generic root=UUID=1e291b4f-afed-45e8-ab4d-25bdbd06707a 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: 07/02/2020 dmi.bios.release: 65.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/02/2020:br65.14:svnDellInc.:pnDellPrecisionM3800:pvrA14:rvnDellInc.:rnDellPrecisionM3800:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:pfa: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. ** 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/2150737 Title: M3800 keyboard backlight problem ubuntu 26.04 Status in linux package in Ubuntu: New Bug description: Hi, I have a bug related to the keyboard backlight of my DELL M3800. If I use FN + F10 key combinaison all is working good. If I try to use the gnome setting or kde setting, nothing happens. rom1@rom1-M3800:~$ ls /sys/class/leds dell::kbd_backlight input3::capslock input3::numlock input3::scrolllock phy0-led rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/brightness 0 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/max_brightness 2 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/trigger [none] usb-gadget usb-host rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 panic ACAD-online BAT1-charging-or-full BAT1-charging BAT1-full BAT1-charging-blink-full-solid BAT1-charging-orange-full-green mmc0 rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio rfkill2 If I use the key combinaison I can see the value of brightness move from 0 to 2 or 1 and physically the keyboard backlight works well. If I try to force the value to 2 in the brightness using command line, nothing happens and the value foes back to 0. I tried with Ubuntu 26.04, Kubuntu 26.04 and Fedora 44 gnome + kde. All have the same behaviour. Could you please fix this ? Best regards. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: rom1 3768 F.... wireplumber /dev/snd/controlC0: rom1 3768 F.... wireplumber /dev/snd/seq: rom1 3749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 13:07:07 2026 InstallationDate: Installed on 2026-04-24 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Dell Precision M3800 ProcEnviron: LANG=fr_FR.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-15-generic root=UUID=1e291b4f-afed-45e8-ab4d-25bdbd06707a 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: 07/02/2020 dmi.bios.release: 65.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/02/2020:br65.14:svnDellInc.:pnDellPrecisionM3800:pvrA14:rvnDellInc.:rnDellPrecisionM3800:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:pfa: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150737/+subscriptions

[Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Won't Fix Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+subscriptions

[Bug 2107336] Re: Missing upstream commits for LP: #2102181

This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2107336 Title: Missing upstream commits for LP: #2102181 Status in linux package in Ubuntu: New Status in linux source package in Noble: Fix Released Bug description: When applying upstream stable patchset (v6.6.67, v6.12.6) we forgot to include: acea3779b2aa libperf cpumap: Add any, empty and min helpers As a result kernel fails to compile. I am thinking we should include the following 2 commits from upstream as a fix: dcd45b376d0a libperf cpumap: Ensure empty cpumap is NULL from alloc b6b4a62d8525 libperf cpumap: Add any, empty and min helpers Failure: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/30629891/+files/buildlog_ubuntu-noble-amd64.linux_6.8.0-60.62_BUILDING.txt.gz evlist.c: In function ‘__perf_evlist__propagate_maps’: evlist.c:55:21: error: implicit declaration of function ‘perf_cpu_map__is_empty’; did you mean ‘perf_cpu_map__set_nr’? [-Werror=implicit-function-declaration] 55 | if (perf_cpu_map__is_empty(evsel->cpus)) { | ^~~~~~~~~~~~~~~~~~~~~~ | perf_cpu_map__set_nr evlist.c:55:21: error: nested extern declaration of ‘perf_cpu_map__is_empty’ [-Werror=nested-externs] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2107336/+subscriptions

[Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11

This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2067669 Title: Mute/mic LEDs no function on ProBook 440/460 G11 Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook 440/460 G11 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067669/+subscriptions