[Kernel-packages] [Bug 2064483] Re: Ubuntu 24.04 doesn't respect vm.swappiness
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: Ubuntu Noble Importance: Undecided Status: New ** No longer affects: ubuntu ** No longer affects: Ubuntu Noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 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-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This is occurring on the Kubuntu Focus NX Gen 2 as well. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
I can verify that the latest version of Ubiquity from -proposed fixes this problem - I booted Ubuntu Desktop 22.04.1, enabled -proposed on the ISO, installed Ubiquity from -proposed, then did a ZFS+encryption installation. Rebooted, logged in, "sudo apt update" behaves normally, Firefox launches and works properly out of the box, and no errors are present when I log into a TTY. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Committed Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
** Description changed: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. - In order for CUDA compute to work, a kernel module "nvidia-uvm" is - necessary. This module *should* exist in the headless NVIDIA 390 driver. - However, it apparently does not exist - it does not show up in the - output of "lsmod", attempting to modprobe it fails, doing a recursive - grep on /lib/modules/$(uname -r) does not reveal it, and it appears that - the Installable Client Driver is not loading correctly. + In order for CUDA or OpenCL compute to work, a kernel module "nvidia- + uvm" is necessary. This module *should* exist in the headless NVIDIA 390 + driver. However, it apparently does not exist - it does not show up in + the output of "lsmod", attempting to modprobe it fails, doing a + recursive grep on /lib/modules/$(uname -r) does not reveal it, and it + appears that the Installable Client Driver is not loading correctly. From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. ** Summary changed: - nvidia-uvm module does not exist, making CUDA unusable with the 390 driver + nvidia-uvm module does not exist, making CUDA and OpenCL unusable with the 390 driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA and OpenCL unusable with the 390 driver Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. In order for CUDA or OpenCL compute to work, a kernel module "nvidia- uvm" is necessary. This module *should* exist in the headless NVIDIA 390 driver. However, it apparently does not exist - it does not show up in the output of "lsmod", attempting to modprobe it fails, doing a recursive grep on /lib/modules/$(uname -r) does not reveal it, and it appears that the Installable Client Driver is not loading correctly. From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
strace of "clinfo -l" from the machine of the affected user. ** Attachment added: "clinfo_strace.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+attachment/5645158/+files/clinfo_strace.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. In order for CUDA compute to work, a kernel module "nvidia-uvm" is necessary. This module *should* exist in the headless NVIDIA 390 driver. However, it apparently does not exist - it does not show up in the output of "lsmod", attempting to modprobe it fails, doing a recursive grep on /lib/modules/$(uname -r) does not reveal it, and it appears that the Installable Client Driver is not loading correctly. From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006408] [NEW] nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
Public bug reported: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. In order for CUDA compute to work, a kernel module "nvidia-uvm" is necessary. This module *should* exist in the headless NVIDIA 390 driver. However, it apparently does not exist - it does not show up in the output of "lsmod", attempting to modprobe it fails, doing a recursive grep on /lib/modules/$(uname -r) does not reveal it, and it appears that the Installable Client Driver is not loading correctly. >From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006408 Title: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Notice: I have not reproduced this bug myself, nor do I have the needed setup to reproduce this bug. This is a bug report based on info provided to me over IRC. In order for CUDA compute to work, a kernel module "nvidia-uvm" is necessary. This module *should* exist in the headless NVIDIA 390 driver. However, it apparently does not exist - it does not show up in the output of "lsmod", attempting to modprobe it fails, doing a recursive grep on /lib/modules/$(uname -r) does not reveal it, and it appears that the Installable Client Driver is not loading correctly. From my own personal experience, I know that nvidia-uvm *does* exist in recommended driver for an NVIDIA 1050 Ti card, however the 390 driver used with the GTX 570 card does not appear to have the driver, even though the card supports CUDA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
Tested on my HP Elitebook 8570p, with Secure Boot and Broadcom WiFi, following the current test plan. All operations went as expected, WiFi is working properly. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Kinetic: Fix Committed Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Run "sudo apt install bcmwl-kernel-source". 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
** Description changed: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. - 8. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. + 8. Run "sudo apt install bcmwl-kernel-source". 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Kinetic: Fix Committed Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Run "sudo apt install bcmwl-kernel-source". 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to:
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
** Description changed: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. - 8. Reboot. - 9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. + 8. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. + 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Kinetic: Fix Committed Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. 9. Reboot and enroll the MOK, then reboot again. The WiFi adapter should begin working once Ubuntu boots. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
** Description changed: + [Impact] + + With the current state of the DKMS package, if a user attempts to + install any package that includes a third-party driver (Broadcom WiFi, + VirtualBox, v4l2loobpack, etc.), the process of signing the newly built + driver with a MOK key will fail silently. This means that any packages + and hardware that require third-party drivers are currently unusable on + a system with Secure Boot. This bug has been tested and verified to + occur with the bcmwl-kernel-source package, but also is very likely to + affect any other packages that use DKMS modules. + + This fix for this is in the -proposed pocket at the moment, and has been + tested to work. + + [Test plan] + + 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) + 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. + 3. When installation finishes, reboot. + 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. + 5. Enable -proposed. + 6. Update *just* the DKMS package with "sudo apt install dkms". + 7. Disable -proposed. + 8. Reboot. + 9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. + + [Where problems could occur] + + Theoretically, a bug in the code could result in DKMS drivers still not + being signed in some instances (though there are no known instances + where this happens). But as Secure Boot + DKMS is already entirely + broken, even this kind of breakage would be an improvement beyond what + we already have. Given the rather obvious nature of such breakage, + thorough testing should be able to detect it with ease. + + --- + + Original bug reports: + Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: [Impact] With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules. This fix for this is in the -proposed pocket at the moment, and has been tested to work. [Test plan] 1: Obtain a system with UEFI, Secure Boot, and Broadcom WiFi. (If Broadcom WiFi is not an option, install VirtualBox in Step 9 rather than bcmwl-kernel-source.) 2. Install Ubuntu on the system, but do not enable the installation of third-party drivers. 3. When installation finishes, reboot. 4. When the system boots into the Ubuntu desktop, connect to the Internet without WiFi, and update all packages on the system. 5. Enable -proposed. 6. Update *just* the DKMS package with "sudo apt install dkms". 7. Disable -proposed. 8. Reboot. 9. Run "sudo apt install bcmwl-kernel-source". The WiFi module should immediately begin working properly. [Where problems could occur] Theoretically, a bug in the code could result in DKMS drivers still not being signed in some instances (though there are no known instances where this happens). But as Secure Boot + DKMS is already entirely broken, even this kind of breakage would be an improvement beyond what we already have. Given the rather obvious nature of such breakage, thorough testing should be able to detect it with ease. --- Original bug reports: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
At the time of this writing, this fix is still stuck in -proposed. This makes the Lubuntu release notes wrong, as it makes it so that updating the system prior to installing WiFi drivers is not enough, even though it is documented as being enough. Considering that this fix very nearly was hotfixed into the Kinetic ISOs just before release, it might be helpful if this could be pushed through to -updates as soon as possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
To workaround the issue by rebuilding and signing the driver manually: 1: Run "sudo dpkg-reconfigure bcmwl-kernel-source" to rebuild the driver. 2: Run "sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/5.19.0-21-generic/updated/dkms/wl.ko" to sign the driver. 3: Run "sudo modprobe wl" to load the driver. At this point the WiFi module should start working and you should be able to connect to WiFi. Note that this assumes that the wl.ko module is at /lib/modules/5.19.0-21-generic/updated/dkms/wl.ko, however since the user probably hasn't managed to update their kernel yet, it's a safe bet that this is in fact where the module is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
Worthy of note, to get the driver to build so I could sign it, I had to do "sudo dpkg-reconfigure bcmwl-kernel-source", then sign the resulting wl.ko file. So it looks like the driver isn't even building in the first place. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
Also, I was able to manually sign the Broadcom kernel module with kmodsign and now it's accepted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
Installing the Kinetic Final image on a Secure Boot enabled laptop with Broadcom WiFi resulted in the WiFi adapter not being able to be turned on in the newly installed system. Doing "sudo modprobe wl" tells me "Key was rejected by service". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in dkms package in Ubuntu: Confirmed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager
** Description changed: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, - UEFI, no secure boot. Testing done in VirtualBox, BIOS, 4 GB RAM, 50 GB - SSD. OS is Ubuntu Desktop, Kinetic Final ISO. + UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB + disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. - 2. Select "Try Ubuntu" (don't select "Install Ubuntu" if you're in VirtualBox or you won't be able to see important buttons). - 3. Click the application menu, search for "Display", and change the screen resolution to something bigger than 800x600 (I use 1360x768). - 4. Start the installer and proceed with the installation process. - 5. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. - 6. Proceed with the rest of the installation as normal. - 7. Reboot into the newly installed system. - 8. Attempt to log in. + 2. Select "Install Ubuntu" and proceed with the installation process. + 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. + 4. Proceed with the rest of the installation as normal. + 5. Reboot into the newly installed system. + 6. Log in. + 7. Run "sudo apt update" in a terminal. - Expected result: You should be logged in and arrive at a GNOME desktop. + Expected result: The package database should be updated normally. - Actual result: You are immediately dropped back to the login screen/ + Actual result: You are presented with the following errors at the end of + the apt output: - Notes: The fall back to the login screen will occur whether you use - Wayland or Xorg. If you switch to a TTY and log in, you will see an - error related to a missing file, /var/lib/dpkg/status. "sudo apt update" - will error out as a result of this missing file. Running "sudo touch - /var/lib/dpkg/status" will allow "sudo apt update" to function, and you - will then be able to log into the GNOME desktop. + Reading package lists... Error! + E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) + E: Could not open file - open (2: No such file or directory) + E: Problem opening + E: The package lists or status file could not be parsed or opened. + + + Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other - scary junk. At least one of those error messages will be related to - update-manager. - - Once you get past that whole mess, the system seems to work OK (I'm - typing on the VM that I produced this mess on). I still notice a "System - program problem detected" window pop up at least once after booting the - VM, but it otherwise functions normally so far. + scary junk. At least one of those error messages was related to update- + manager in my experience, and another one was from "check-new-release- + gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no username) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no username) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: New Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed
[Kernel-packages] [Bug 1991936] Re: No AAC codec for Pipewire on Ubuntu Kinetic
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1991936 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: linux (Ubuntu) => pipewire (Ubuntu) ** Changed in: pipewire (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991936 Title: No AAC codec for Pipewire on Ubuntu Kinetic Status in pipewire package in Ubuntu: Confirmed Bug description: The AAC codec is not showing up in the sound settings when a device that is capable of that codec is connected, but other supported codecs do work.Tested using the Sony WH1000XM4 and other bluetooth devices that support the codec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1991936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990068] Re: Kernel 5.19.0.15.15 crashes on boot (Ryzen 5 2500U)
Loading initial ramdisk... you don't happen to see an "Out of memory" error when that happens, do you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990068 Title: Kernel 5.19.0.15.15 crashes on boot (Ryzen 5 2500U) Status in linux package in Ubuntu: Confirmed Bug description: When installing the daily build ISO fo Ubuntu Kinect Kudu, the system will hang at boot, forcing a reboot and then going to Advanced Option (on GRUB) and selection kernel 5.15.0.27.28, which comes preinstalled when Ubuntu is installed, which then works as usual. Testing with different Kernel versions shows that 5.18.19 works fine, without crashing on "Loading initial ramdisk...". This, unfortunately, won't create a single log file or crash dump, which makes error reporting hard, to say the least. System info: Laptop model: Lenovo ideapad 330S-15ARR CPU: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx x8 GPU: AMD Radeon Vega 8 Graphics RAM: 12GB - 2400MHz Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Also, it is always necessary to add the "iommu=soft" command to the GRUB_CMDLINE_LINUX_DEFAULT line on /etc/default/grub, because no kernels will boot without it (this is an older issue). Even with this command, Kernel 5.19.X will always crash while loading the initial ramdisk. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matheus1693 F wireplumber /dev/snd/controlC0: matheus1693 F wireplumber /dev/snd/seq:matheus1690 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: LENOVO 81JQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=45a8c70a-d30e-4f97-ab4f-e761450b6302 ro quiet splash iommu=soft rcu_nocbs=0-7 processor.max_cstate=1 nopti pti=off amdgpu.gpu_recovery=1 ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet amd_iommu=on amdgpu.dc=1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220819.git8413c63c-0ubuntu2 Tags: kinetic wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvr7WCN38WW:bd11/04/2019:br1.38:efr1.38:svnLENOVO:pn81JQ:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:skuLENOVO_MT_81JQ_BU_idea_FM_ideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81JQ dmi.product.sku: LENOVO_MT_81JQ_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983787] Re: USB hub only works in USB2 ports
Can you boot into an older kernel and see if it works right there? Also, it might be interesting if you could plug in your hub into a USB 3 port, try to use it, unplug it, then run "sudo dmesg > dmesg.txt" in a terminal and attach the dmesg.txt file generated by doing this. That will give us info about what the kernel does when you plug the hub in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983787 Title: USB hub only works in USB2 ports Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: I have an IOGear GUS404 USB hub/switch (https://www.iogear.com/product/GUS404/), which works only when plugged into a USB2.0 port. When plugged into a USB3.0 port, none of the attached peripherals work. The attached peripherals are: 1) Corsair Vengeance K70 RGB Keyboard (https://www.corsair.com/us/en/Categories/Products/Gaming- Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical- Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA) 2) Logitech G9x Mouse (https://www.newegg.com/logitech-g9x/p/N82E16826104261) 3) Logitech C922 Webcam (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam- for-hd-video-streaming-black/5579380.p?skuId=5579380) Ubuntu release: ~$ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Aug 7 15:57:21 2022 InstallationDate: Installed on 2022-06-11 (57 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983346] Re: Launch Pad is not detected by Linux Kernel
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thank you! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983346 Title: Launch Pad is not detected by Linux Kernel Status in linux package in Ubuntu: Incomplete Bug description: Launch Pad is not detected by Linux Kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chinnu 1503 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue Aug 2 13:36:20 2022 InstallationDate: Installed on 2022-07-31 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81WD ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=94b92838-1dcd-4959-90c6-8adc04fa36d0 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-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:br1.13:efr1.13:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05:skuLENOVO_MT_81WD_BU_idea_FM_IdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982986] Re: Black screen on Linux 5.19.0
Thanks for taking the time to report this bug. However, Ubuntu only supports kernels that are included in Ubuntu. Linux 5.19 is not available in Ubuntu yet through any official channel, and the bug report info itself states "The running kernel is not an Ubuntu kernel". Only Ubuntu kernels are handled here. However, if this is a reproducible bug, and you can reproduce it with the absolute latest kernels (preferably compiled from source yourself), I'd report the bug to the Linux developers themselves. Info on how to do so is here: https://www.kernel.org/doc/html/v4.19/admin-guide/reporting- bugs.html Closing as invalid and converting to a question. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/702577 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982986 Title: Black screen on Linux 5.19.0 Status in linux package in Ubuntu: Invalid Bug description: I'm trying to test Linux 5.19 using the packages released for Ubuntu Kinetic (the version I'm using right now), but I almost always get a black screen. First I thought it was NVIDIA kernel module (because I'm using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with NVIDIA GPU as off-load) everything worked correctly, but the problem seems related to i915 module. --- ProblemType: Bug ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-11-26 (243 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: kinetic Uname: Linux 5.18.14-051814-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to kinetic on 2022-06-14 (43 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982826] Re: Boot freeze on hyper-v instance
You may be able to determine why the system is freezing by manually editing the kernel command line in GRUB and removing the "quiet splash" part of the command line. Then boot with this modified command line. This will make the Linux kernel print debugging information to your screen - this will tell you the last successful step of the boot process, and it may give you a kernel panic message, which contains a wealth of debugging data, and may even give you the solution to the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1982826 Title: Boot freeze on hyper-v instance Status in linux-signed-azure package in Ubuntu: New Bug description: After upgrade to this version of kernel, the hyper-v instance of ubuntu 20.04.4 (on windows server 2022) freeze on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/1982826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981907] Re: Errors were encountered while processing: linux-image-5.13.0-44-generic
Did you tweak /etc/default/grub by any chance? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981907 Title: Errors were encountered while processing: linux- image-5.13.0-44-generic Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-5.13.0-51-generic linux-hwe-5.13-headers-5.13.0-51 linux-image-5.13.0-51-generic linux-modules-5.13.0-51-generic linux-modules-extra-5.13.0-51-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: linux-image-unsigned-5.13.0-44-generic Suggested packages: fdutils linux-doc | linux-hwe-5.13-source-5.13.0 linux-hwe-5.13-tools linux-headers-5.13.0-44-generic linux-modules-extra-5.13.0-44-generic The following packages will be REMOVED: linux-image-5.13.0-44-generic The following NEW packages will be installed: linux-image-unsigned-5.13.0-44-generic 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/10.1 MB of archives. After this operation, 283 kB of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: linux-image-5.13.0-44-generic: dependency problems, but removing anyway as you requested: linux-modules-5.13.0-44-generic depends on linux-image-5.13.0-44-generic | linux-image-unsigned-5.13.0-44-generic; however: Package linux-image-5.13.0-44-generic is to be removed. Package linux-image-unsigned-5.13.0-44-generic is not installed. (Reading database ... 238004 files and directories currently installed.) Removing linux-image-5.13.0-44-generic (5.13.0-44.49~20.04.1) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-44-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-41-generic Found initrd image: /boot/initrd.img-5.15.0-41-generic Found linux image: /boot/vmlinuz-5.13.0-51-generic Found initrd image: /boot/initrd.img-5.13.0-51-generic Found linux image: /boot/vmlinuz-5.13.0-48-generic Found initrd image: /boot/initrd.img-5.13.0-48-generic Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings error: $. error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 331 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-5.13.0-44-generic (--remove): installed linux-image-5.13.0-44-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-5.13.0-44-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 00:20:03 2022 InstallationDate: Installed on 2022-02-03 (162 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981727] Re: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1981727 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981727 Title: kernel 5.15.0-41 update results in dim screen (5.13.0-52 OK) Status in linux-hwe-5.15 package in Ubuntu: New Bug description: A recent update to 5.15.0-41 results in my laptop screen (Dell Precision 7520) being unable to come up to full brightness. I have verified that I can revert to 5.13.0-52 and the problem is not there. I looked at /sys/class/backlight/nv_backlight/max_brightness which lists 1023 in the newer kernel and 100 in the older one. I have verified that changing the brightness manually does change /sys/class/backlight/nv_backlight/brightness, all the way up to 1023, but it's just not enough... the screen is still very dim. The other screen (standalone monitor through docking station) on a two-headed display is fine. I tried to write 100 into max_brightness but of course, the "file" is read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1981727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981589] Re: dell latitude 3400 touchpad not detected
Could you attach the output of the commands "lspci" and "lsusb" to your report? This is almost without question a hardware-specific problem, so knowing the hardware involved would be helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981589 Title: dell latitude 3400 touchpad not detected Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: touchpad not detected and work only after connecting usb mouse, touchpad features don't work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-121.137~18.04.1-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 19:13:11 2022 InstallationDate: Installed on 2020-12-06 (584 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1981589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I don't believe that my system ever was able to wake from the touchpad - I seem to remember having to use the power button or open the lid in the past. I thought maybe I just had something misconfigured back then, but maybe not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I installed the same kernel that is in 20.04 onto a Lubuntu Kinetic (22.10 alpha) installation, and the touchpad wake didn't work on my laptop. I then tried USB wake on the kernel that's part of Kinetic, and USB wake did work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Sadly, I have to correct myself - I thought I had replicated the issue, but it turns out my particular laptop doesn't use USB to attach the mousepad. I tried plugging a USB mouse into my system while running a "bad" kernel, and it was able to wake from suspend when I moved the mouse. Also, it appears my system is using s2idle. So sadly, I cannot reproduce the bug on my hardware after all. What I can do is leave a hint for the next person who goes to bisect the kernel. Due to a change in initrd compression, if you try to install a kernel that's too old onto Ubuntu Jammy or Kinetic, it won't be able to boot since it won't be able to mount the initrd image. To fix this, do "sudo nano /etc/initramfs-tools/initramfs.conf", and change the "COMPRESS" option to "gzip" (it will probably be set to "zstd" by default). That should get your older kernels booting, so you can actually have a fighting chance at bisecting the kernel. Sorry I couldn't do it myself on my hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
@chromastone I have experience with building software from source, and have a laptop that replicates the problem. I'll give it a shot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Successfully replicated this bug on an HP Elitebook 8570p, 16 GB RAM, Intel i5-3210M (if dmidecode is not deceiving me). I also cannot get the touchpad to cause the system to wake from suspend even trying to enable the wakeup files for all three of the USB controllers in my system. OS is the latest Lubuntu Kinetic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971933] Re: Unable to wake laptop using trackpad input
** Tags added: kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: Unable to wake laptop using trackpad input Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 22.04, the dell laptop no longer wakes up using trackpad movement/interaction. Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e., Working On: Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10. NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 ) Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend, But, Trackpad trigger to wakeup from suspend is not working. -- $ cat /proc/version_signature > version.log => Ubuntu 5.15.0-27.28-generic 5.15.30 - $ lsb_release -rd => Description:Ubuntu 22.04 LTS Release:22.04 - $ apt-cache policy linux-image-generic => linux-image-generic: Installed: 5.15.0.27.30 Candidate: 5.15.0.27.30 Version table: *** 5.15.0.27.30 500 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages - What I expected to happen: Laptop wakes-up from suspend on touchpad interaction - What happened: Laptop did not wakeup from suspend on touchpad interaction. Laptop woke up on the press of power button. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.27.30 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monkey 5198 F wireplumber /dev/snd/controlC1: monkey 5198 F wireplumber /dev/snd/seq:monkey 5195 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 6 12:40:22 2022 InstallationDate: Installed on 2018-10-25 (1288 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 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-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
