[Kernel-packages] [Bug 1857764] Re: [nvidia] Brightness control is not working since last update
installed in Vaio vpceh25en having Nvidia Geforce 410M and brightness controller not working neither from slider nor from the keyboard. Also, the display looks dull and pixelated. -- 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/1857764 Title: [nvidia] Brightness control is not working since last update Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: The brightness control is not working since last update ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 10:14:13 2019 DistUpgraded: 2019-10-22 22:53:56,942 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 390.129, 5.0.0-32-generic, x86_64: installed nvidia, 390.129, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1bc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bc0] InstallationDate: Installed on 2019-01-28 (334 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=eba46c54-e23c-4792-ac66-515a492a45d9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (66 days ago) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.307:bd03/14/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857764/+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 1787281] Re: errors when scanning partition table of corrupted AIX disk
Hey,
I am so sorry, I accidentally changed the status of this bug. I
apologize for the inconvenience. please rollback my status change.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1787281
Title:
errors when scanning partition table of corrupted AIX disk
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Precise:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Bug description:
[Impact]
* Users with disks/LUNs used for AIX operating system installations
previously, which possibly undergone overwrites/corruption on the
partition table, might hit kernel failures during partition scan
of such disk/LUN, and possibly hang the system (seen with retries).
* The Linux kernel should be robust to corrupted disk data, performing
a better sanitization/checks and not failing.
* The fix are a couple of simple logic changes to make the code
of the AIX partition table parser more robust.
[Test Case]
* Run the partition scan on the (trimmed) disk image of the AIX lun.
(It's not provided here since it contains customer data), with this
command:
$ sudo losetup --find --show --partscan rlv_grkgld.1mb
* On failure, the command hangs, and messages like these are printed
to the console, depending on the kernel version (see tests below)
[ 270.506420] partition (null) (3 pp's found) is not contiguous
[ 270.597428] BUG: unable to handle kernel paging request at
1000
[ 270.599525] IP: [] strnlen+0xd/0x40
* On success, the command prints a loop device name, for example:
/dev/loop0
[Regression Potential]
* Low. Both changes are simple improvements in logic.
* This affects users which mount disks/LUNs from the AIX OS;
it should only change behavior for users which relied on a
uninitialized variables to work correctly during partition
scan of those disks/LUNs which should be rare as the code
is likely to fail as we observe in this scenario.
* This has been tested on Cosmic, Bionic, Xenial, and Trusty.
[Other Info]
* Patches will be sent to the kernel-team mailing list.
Bug Description:
---
We've recently received a disk image from an AIX LUN that when
attached on Linux displayed errors on console, then eventually
hung the system (specially if the SCSI bus was re-scanned, and
leading to another partition scan).
Apparently the LUN was originally installed with AIX and later
exercised with some I/O stress/overwrites which caused certain
bits to be wrong in just the right way for Linux to get a NULL
pointer and invalid data.
This is the test-case used ('--partscan' is the important bit).
$ sudo losetup --show --find --partscan aix-lun.img
Since the original code is old, it affects several releases.
It's interesting to fix this on 14.04 and up, on which IBM
Power servers were initially supported (since they can run
AIX too, and possibly hit this due to an already used disk/LUN).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787281/+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 1667046] Re: CVE-2017-6074 DCCP vulnerability
Hey, Does this affects the new version of kernel as well. Or is it restricted to the 2.6 versions. -- 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/1667046 Title: CVE-2017-6074 DCCP vulnerability Status in linux package in Ubuntu: Fix Released Bug description: CVE-2017-6074 was made public today as a DCCP double-free vulnerability that could allow for kernel code execution from an unprivileged process. This local root vulnerability is present in Linux kernel releases going back at least to 2006 but potentially to 2005 when the code was first introduced. It affects kernel builds with CONFIG_IP_DCCP. Fixed upstream https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5edabca9d4cff7f1f2b68f0bac55ef99d9798ba4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667046/+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 1428637] [NEW] package linux-image-extra-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers
Public bug reported: Shows error popup on desktop just after the system is ready ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.77 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohit 3612 F pulseaudio Date: Tue Mar 3 13:46:00 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.77:cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko.dpkg-new': unexpected end of file or stream HibernationDevice: RESUME=UUID=b3ad47ca-1fa2-486d-a495-f74f87674da0 InstallationDate: Installed on 2014-08-05 (212 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=03fb9061-868f-4a5e-aa79-76282071efd2 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: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to trusty on 2015-01-15 (49 days ago) dmi.bios.date: 08/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/12/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1428637 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko .dpkg-new': unexpected end of file or stream Status in linux package in Ubuntu: New Bug description: Shows error popup on desktop just after the system is ready ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.77 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohit 3612 F pulseaudio Date: Tue Mar 3 13:46:00 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.77:cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko' to '/lib/modules/3.13.0-46-generic/kernel/drivers/staging/dgnc/dgnc.ko.dpkg-new': unexpected end of file or stream HibernationDevice: RESUME=UUID=b3ad47ca-1fa2-486d-a495-f74f87674da0 InstallationDate: Installed on 2014-08-05 (212 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=03fb9061-868f-4a5e-aa79-76282071efd2 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: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: ca
[Kernel-packages] [Bug 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
How do you prevent the machine from using 2.4GHz? It seems that they removed that selector from the plasma nm client. -- 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/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? Core Info: * Ubuntu 24.10 * Pixel Buds Pro 2 earbuds * 6.11 kernel default with 24.10 * AX211 CNVi wifi/bt integrated onto motherboard * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092655/+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 2092655] [NEW] Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
Public bug reported: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in bluez package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2092655/+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 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
** Description changed: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? + + Core Info: + * Ubuntu 24.10 + * Pixel Buds Pro 2 earbuds + * 6.11 kernel default with 24.10 + * AX211 CNVi wifi/bt integrated onto motherboard + * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) + * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in bluez package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? Core Info: * Ubuntu 24.10 * Pixel Buds Pro 2 earbuds * 6.11 kernel default with 24.10 * AX211 CNVi wifi/bt integrated onto motherboard * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2092655/+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 2081384] Re: bluetooth headphones need reconnect after every reboot
I can confirm that this fixed this bug for me too with the package in proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2081384 Title: bluetooth headphones need reconnect after every reboot Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bluez source package in Oracular: Confirmed Status in linux source package in Oracular: Confirmed Bug description: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:00 desktop bluetoothd[3274]: No matching connection for device 23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress 23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:15:46 desktop bluetoothd[3274]: /org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready In dmesg I see lots of: [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+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 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
I am having wifi disconnects too so I think it might be related to these issues. 1. https://bbs.archlinux.org/viewtopic.php?id=300446 2. https://bbs.archlinux.org/viewtopic.php?id=300120 I think there might be some bugs in the kernel drivers for AX211 wifi and bt -- 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/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? Core Info: * Ubuntu 24.10 * Pixel Buds Pro 2 earbuds * 6.11 kernel default with 24.10 * AX211 CNVi wifi/bt integrated onto motherboard * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092655/+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 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
Thanks for the follow up. Here's what I tried and the results: I set up a 5GHz and 6GHz network and I still have problems with the disconnects I tried: bluetoothctl # scan off # Failed to stop discovery: org.bluez.Error.Failed I can't turn scan off and this seems to be common when I do a bit of googling. Any other advice? I am surprised that the steam deck doesn't have the same issues as it's probably in a similar stack. -- 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/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? Core Info: * Ubuntu 24.10 * Pixel Buds Pro 2 earbuds * 6.11 kernel default with 24.10 * AX211 CNVi wifi/bt integrated onto motherboard * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092655/+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 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes
Is there a way to set the pipewire buffer length? I would try with a newer kernel but the mainline kernel ppa isn't updating again. Seems like something is broken on the ppa. -- 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/2092655 Title: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the desktop environment switches from my headphones to the speaker and back to the headphones within the span of 5 seconds. This happens quite frequently and even when audio is playing. The syslog shows: 2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110) 2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: org.bluez.Error.Failed 2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event) 2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: (bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event) 2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" 2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: No object for name "bluez_output.24_95_2F_AF_2A_3D.1" At the exact time that these dropouts happen. The same earbuds work fine on android and on the steam deck so I think the problem is with the laptop setup. Can anyone help? Core Info: * Ubuntu 24.10 * Pixel Buds Pro 2 earbuds * 6.11 kernel default with 24.10 * AX211 CNVi wifi/bt integrated onto motherboard * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos) * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092655/+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 1855845] [NEW] Touch pad not working for the model Dell Inspiron 5447
Public bug reported: Don know about the touch pad manufacturer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rohit 1690 F pulseaudio /dev/snd/controlC0: rohit 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 10 13:54:33 2019 HibernationDevice: RESUME=UUID=7d5b4014-1dd0-4e1b-a952-83839faf0b81 InstallationDate: Installed on 2018-11-26 (378 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=23c88e17-589a-4acf-8a5a-2fc53651c506 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JG3PJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/08/2018:svnDellInc.:pnInspiron5447:pvrA12:rvnDellInc.:rn0JG3PJ:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1855845 Title: Touch pad not working for the model Dell Inspiron 5447 Status in linux package in Ubuntu: New Bug description: Don know about the touch pad manufacturer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rohit 1690 F pulseaudio /dev/snd/controlC0: rohit 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 10 13:54:33 2019 HibernationDevice: RESUME=UUID=7d5b4014-1dd0-4e1b-a952-83839faf0b81 InstallationDate: Installed on 2018-11-26 (378 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=23c88e17-589a-4acf-8a5a-2fc53651c506 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JG3PJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/08/2018:svnDellInc.:pnInspiron5447:pvrA12:rvnDellInc.:rn0JG3PJ:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855845/+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
Re: [Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Hello Nilesh, Amazing bro. It worked flawlessly . I was literally pissed off upgrading/downgrading kernels and doing shitty troubleshootings. thanks a lot man . You literally saved my day. regards, Rohit On Mon, Dec 30, 2019 at 3:30 PM Nilesh Pansuriya <1854...@bugs.launchpad.net> wrote: > Follow this steps, it works for me: > > 1. Run > $ sudo -H gedit /etc/default/grub > > In the open window edit line > > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" > > it should look this way > > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp" > > Save file and run > > $ sudo update-grub > > 2. Run > $ echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf > $ sudo depmod -a > $ sudo update-initramfs -u > $ echo "synaptics_i2c" | sudo tee -a /etc/modules > > 3. Reboot. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1855845). > https://bugs.launchpad.net/bugs/1854798 > > Title: > Synaptics s3203 touchpad not working after update to kernel > 4.15.0-72-generic > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Bionic: > Confirmed > > Bug description: > SRU justification > = > [Impact] > Synaptics s3203 touchpad not working after update to kernel > 4.15.0-72-generic > > [Fix] > After applied commit "Input: synaptics-rmi4 - avoid processing unknown > IRQs", > no irq response from touchpad. > This commit is depended on commit: > "Input: synaptics-rmi4 - convert irq distribution to irq_domain" > > [Test] > Verified on hardware, tests results are good. > > [Regression Potential] > Low. > Fix bug that introduced by stable release update. > > 2nd and 3rd patches are fixes for the 1st patch. > These commits are already included by eoan kernel, so bionic 4.15 only. > > Original reports > === > > environment: > Dell Laptop XPS-9333 > Device: > # xinput --list > ⎡ Virtual core pointerid=2[master pointer > (3)] > ⎜ ↳ Virtual core XTEST pointer id=4[slave > pointer (2)] > ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave > pointer (2)] > ⎜ ↳ Synaptics s3203 id=12 [slave > pointer (2)] > ⎜ ↳ Ultrathin Touch Mouse id=11 [slave > pointer (2)] > ⎣ Virtual core keyboard id=3[master keyboard > (2)] > ↳ Virtual core XTEST keyboard id=5[slave > keyboard (3)] > ↳ Dell WMI hotkeysid=13 [slave > keyboard (3)] > ↳ AT Translated Set 2 keyboardid=14 [slave > keyboard (3)] > ↳ Integrated_Webcam_HD: Integrate id=10 [slave > keyboard (3)] > ↳ DELL Wireless hotkeys id=15 [slave > keyboard (3)] > ↳ Video Bus id=7[slave > keyboard (3)] > ↳ Power Buttonid=8[slave > keyboard (3)] > ↳ Power Buttonid=6[slave > keyboard (3)] > > # xinput --list-props 12 > Device 'Synaptics s3203': >Device Enabled (142):1 >Coordinate Transformation Matrix (144): 1.00, 0.00, > 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 >Device Accel Profile (270): 1 >Device Accel Constant Deceleration (271):2.50 >Device Accel Adaptive Deceleration (272):1.00 >Device Accel Velocity Scaling (273): 9.712231 >Synaptics Edges (304): 162, 3908, 133, 2339 >Synaptics Finger (305): 25, 30, 0 >Synaptics Tap Time (306):180 >Synaptics Tap Move (307):209 >Synaptics Tap Durations (308): 180, 180, 100 >Synaptics ClickPad (309):1 >Synaptics Middle Button Timeout (310): 0 >Synaptics Two-Finger Pressure (311): 282 >Synaptics Two-Finger Width (312):7 >Synaptics Scrolling Distance (313): -95, 95 >Synaptics Edge Scrolling (314): 0, 0, 0 >Synaptics Two-Finger Scrolling (315):1, 1 >Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 >Synaptics Off (317): 0 >Synaptics Locked Drags (318):0 >Synaptics Locked Drags Timeout (319):5000 >Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 >Synaptics Click Acti
[Kernel-packages] [Bug 1849369] [NEW] Ubuntu 19.10 ARM64 kernel has KVM disabled by default
Public bug reported: Using the official Ubuntu 19.10 arm64 image, http://cdimage.ubuntu.com/ubuntu/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz, with the 5.3.x Linux kernel has KVM/VIRTUALIZATION disabled by default and therefore /dev/kvm acceleration is not available on installations on newer Raspberry Pi 4 (for example) which has a supported processor (armv8) by KVM (https://www.linux-kvm.org/page/Processor_support#ARM:). I'm able to compile the kernel manually with the options enabled in the kernel config (http://dl.rohityadav.cloud/cloudstack-rpi/kernel-19.10/) and further verify that it works well in deploying ARM64 VMs (http://dl.rohityadav.cloud/cloudstack-rpi/template/). I went a bit further to deploy an Apache CloudStack based IaaS deployment and verify that it works as well. Having KVM enabled arm64 devices would enable testing and misc use-cases on newer boards such as the Raspberry Pi 4 (4 GB RAM). Can the Ubuntu kernel team advise why KVM is not enabled in the kernel by default, and if this will change in future? Thanks. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: arm64 kernel kvm pi raspberry ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849369 Title: Ubuntu 19.10 ARM64 kernel has KVM disabled by default Status in linux-raspi2 package in Ubuntu: New Bug description: Using the official Ubuntu 19.10 arm64 image, http://cdimage.ubuntu.com/ubuntu/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz, with the 5.3.x Linux kernel has KVM/VIRTUALIZATION disabled by default and therefore /dev/kvm acceleration is not available on installations on newer Raspberry Pi 4 (for example) which has a supported processor (armv8) by KVM (https://www.linux-kvm.org/page/Processor_support#ARM:). I'm able to compile the kernel manually with the options enabled in the kernel config (http://dl.rohityadav.cloud/cloudstack- rpi/kernel-19.10/) and further verify that it works well in deploying ARM64 VMs (http://dl.rohityadav.cloud/cloudstack-rpi/template/). I went a bit further to deploy an Apache CloudStack based IaaS deployment and verify that it works as well. Having KVM enabled arm64 devices would enable testing and misc use-cases on newer boards such as the Raspberry Pi 4 (4 GB RAM). Can the Ubuntu kernel team advise why KVM is not enabled in the kernel by default, and if this will change in future? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369/+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 1848790] Re: USB not working under arm64 on Pi4
@hui.wang - thanks, seems to work but /dev/kvm is missing. Can you advise why the kernels are not built by default with KVM/VIRTUALIZATION enabled in the kernel config? If this going to change in future. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1849369] Re: Ubuntu 19.10 ARM64 kernel has KVM disabled by default
*** This bug is a duplicate of bug 1783961 *** https://bugs.launchpad.net/bugs/1783961 ** This bug has been marked a duplicate of bug 1783961 CONFIG_KVM is disabled for linux-raspi2 (aarch64) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849369 Title: Ubuntu 19.10 ARM64 kernel has KVM disabled by default Status in linux-raspi2 package in Ubuntu: New Bug description: Using the official Ubuntu 19.10 arm64 image, http://cdimage.ubuntu.com/ubuntu/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz, with the 5.3.x Linux kernel has KVM/VIRTUALIZATION disabled by default and therefore /dev/kvm acceleration is not available on installations on newer Raspberry Pi 4 (for example) which has a supported processor (armv8) by KVM (https://www.linux-kvm.org/page/Processor_support#ARM:). I'm able to compile the kernel manually with the options enabled in the kernel config (http://dl.rohityadav.cloud/cloudstack- rpi/kernel-19.10/) and further verify that it works well in deploying ARM64 VMs (http://dl.rohityadav.cloud/cloudstack-rpi/template/). I went a bit further to deploy an Apache CloudStack based IaaS deployment and verify that it works as well. Having KVM enabled arm64 devices would enable testing and misc use-cases on newer boards such as the Raspberry Pi 4 (4 GB RAM). Can the Ubuntu kernel team advise why KVM is not enabled in the kernel by default, and if this will change in future? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369/+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 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
Just found this bug, I had added a similar bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369 (now marked as duplicate). Copy paste from above: Using the official Ubuntu 19.10 arm64 image, http://cdimage.ubuntu.com/ubuntu/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz, with the 5.3.x Linux kernel has KVM/VIRTUALIZATION disabled by default and therefore /dev/kvm acceleration is not available on installations on newer Raspberry Pi 4 (for example) which has a supported processor (armv8) by KVM (https://www.linux-kvm.org/page/Processor_support#ARM:). I'm able to compile the kernel manually with the options enabled in the kernel config (http://dl.rohityadav.cloud/cloudstack-rpi/kernel-19.10/) and further verify that it works well in deploying ARM64 VMs (http://dl.rohityadav.cloud/cloudstack-rpi/template/). I went a bit further to deploy an Apache CloudStack based IaaS deployment and verify that it works as well. Having KVM enabled arm64 devices would enable testing and misc use-cases on newer boards such as the Raspberry Pi 4 (4 GB RAM). Can the Ubuntu kernel team advise why KVM is not enabled in the kernel by default, and if this will change in future? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
Great, thanks @hui.wang. I'll test it in the evening and keep you posted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1848790] Re: USB not working under arm64 on Pi4
@hui.wang - I'm not sure on RPi3, but Ubuntu 18.04+KVM certainly works on RPi4. See someone already blogged about this here: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3 -image-unofficial, I tried their image but it had issues due to older libvirt/qemu versions on 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1848790] Re: USB not working under arm64 on Pi4
@hui.wang - I tested the compiled kernel on my RaspberryPi4 (4GB RAM model). Both KVM and external SSD/USB (in my case Samsung T5, 500GB external SSD) on the USB 3.0 port are working fine: root@cloudstack-mgmt:~# ls /dev/kvm /dev/kvm root@cloudstack-mgmt:~# kvm-ok INFO: /dev/kvm exists KVM acceleration can be used root@cloudstack-mgmt:~# lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # fdisk -l [.. snipped ..] Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors Disk model: Portable SSD T5 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 33553920 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sda12048 976773134 976771087 465.8G c W95 FAT32 (LBA) root@cloudstack-mgmt:~# blkid -o list device fs_type label mount pointUUID --- /dev/mmcblk0p1 vfatsystem-boot /boot/firmware 79A2-EC62 /dev/mmcblk0p2 ext4writable / 2fae1f20-4a20-4c77-a39b-fb6480f64a0b /dev/loop0 squashfs /snap/lxd/12210 /dev/loop1 squashfs /snap/core/7920 /dev/sda1 ext4 (not mounted) 91175b3a-ee2c-47a7-a1e5-f4528e127523 This confirms that the patch and kernel-image build by @hui.wang fixes the external USB storage issue with the 4GB RPi4 model. Thanks @hui.wang. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
@hui.wang and the Ubuntu kernel team - kindly consider enabling KVM for arm64 Linux kernel in the raspberrypi preinstalled image in future. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
@hui.wang - I tested the compiled kernel on my RaspberryPi4 (4GB RAM model). Both KVM and external SSD/USB (in my case Samsung T5, 500GB external SSD) on the USB 3.0 port are working fine. root@cloudstack-mgmt:~# ls /dev/kvm /dev/kvm root@cloudstack-mgmt:~# kvm-ok INFO: /dev/kvm exists KVM acceleration can be used Further description of how KVM was tested is here along with Apache CloudStack (an IaaS platform): https://github.com/rhtyd/rhtyd.github.io/blob/master/_drafts/2019-10-22-cloudstack-rpi4-kvm.markdown Tested using guest templates Debian 9 and Debian 10, both arm64 - http://dl.rohityadav.cloud/cloudstack-rpi/template/ Tested/issues: - Only scsi seems to be the working disk controller (ide is not supported, virtio may/may not work) - when testing with linux guests. Workaround: use scsi by default. - Plugging in usb devices without an explicit controller added first, fails (on x86_64 systems, controller seems to be already added when usb devices like keyboard/mouse etc are added). Workaround: add a usb controller and then add the usb devices - keyboard, mouse, tablet. I've attached some screenshots of a guest VM running on the RPi4 device using CloudStack. ** Attachment added: "Screenshot from 2019-10-23 18-22-59.png" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+attachment/5299489/+files/Screenshot%20from%202019-10-23%2018-22-59.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1810767] [NEW] package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: check report file( fix broken install issue) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-image-4.15.0-24-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jan 7 16:14:00 2019 DpkgHistoryLog: Start-Date: 2019-01-07 16:13:57 Commandline: apt --fix-broken install Requested-By: vtplphp2 (1000) Install: linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-07-03 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1810767 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in linux-signed package in Ubuntu: New Bug description: check report file( fix broken install issue) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-image-4.15.0-24-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jan 7 16:14:00 2019 DpkgHistoryLog: Start-Date: 2019-01-07 16:13:57 Commandline: apt --fix-broken install Requested-By: vtplphp2 (1000) Install: linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-07-03 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1810767/+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 1638025] [NEW] MT7601U module crashes with 4.4.0.45 Kernel
Public bug reported: There are frequent crash seen with MT7601U module with latest kernel 4.4.0.45. [ 135.900428] [ cut here ] [ 135.900434] WARNING: CPU: 1 PID: 13 at /build/linux-kOWph6/linux-4.4.0/drivers/net/wireless/mediatek/mt7601u/dma.c:291 mt7601u_dma_enqueue_tx+0x26b/0x2a0 [mt7601u]() [ 135.900435] Modules linked in: [ 135.900436] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900437] ip6table_filter [ 135.900439] ip6_tables iptable_filter [ 135.900440] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900441] ip_tables x_tables drbg ansi_cprng ctr ccm arc4 mt7601u mac80211 cfg80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp nls_iso8859_1 kvm_intel kvm rndis_host cdc_ether irqbypass usbnet snd_hda_codec_hdmi snd_hda_codec_realtek crct10dif_pclmul crc32_pclmul snd_hda_codec_generic snd_hda_intel aesni_intel aes_x86_64 joydev snd_hda_codec input_leds lrw snd_hda_core gf128mul snd_hwdep glue_helper snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ablk_helper snd_timer snd serio_raw soundcore cryptd mei_me mei shpchp lpc_ich mac_hid tpm_infineon 8250_fintek parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid i915 i2c_algo_bit [ 135.900472] drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops drm ahci r8169 libahci mii video fjes [ 135.900478] CPU: 1 PID: 13 Comm: ksoftirqd/1 Tainted: GW 4.4.0-45-generic #66-Ubuntu [ 135.900479] Hardware name: Gigabyte Technology Co., Ltd. H81M-S2PH/H81M-S2PH, BIOS FC 11/10/2014 [ 135.900480] 0086 489d46bf 880215b3f970 813f1fe3 [ 135.900483] c04ec118 880215b3f9a8 81081212 [ 135.900485] 880035716858 880210e32898 0005 8800d0dc8d00 [ 135.900487] Call Trace: [ 135.900490] [] dump_stack+0x63/0x90 [ 135.900492] [] warn_slowpath_common+0x82/0xc0 [ 135.900494] [] warn_slowpath_null+0x1a/0x20 [ 135.900498] [] mt7601u_dma_enqueue_tx+0x26b/0x2a0 [mt7601u] [ 135.900511] [] ? minstrel_ht_get_rate+0x34/0x4c0 [mac80211] [ 135.900516] [] mt7601u_tx+0x223/0x3c0 [mt7601u] [ 135.900528] [] ? ieee80211_crypto_ccmp_encrypt+0x34/0x250 [mac80211] [ 135.900540] [] ieee80211_tx_frags+0x170/0x3b0 [mac80211] [ 135.900552] [] __ieee80211_tx+0x81/0x180 [mac80211] [ 135.900554] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900569] [] ieee80211_tx+0xdf/0x110 [mac80211] [ 135.900582] [] ieee80211_xmit+0x9b/0xf0 [mac80211] [ 135.900594] [] __ieee80211_subif_start_xmit+0x55b/0x790 [mac80211] [ 135.900598] [] ? csum_partial_ext+0x9/0x10 [ 135.900604] [] ? __skb_checksum+0x65/0x2d0 [ 135.900608] [] ? select_idle_sibling+0xef/0x120 [ 135.900613] [] ? kfree_skbmem+0x59/0x60 [ 135.900617] [] ? consume_skb+0x34/0x90 [ 135.900622] [] ? packet_rcv+0x44/0x440 [ 135.900634] [] ieee80211_subif_start_xmit+0x10/0x20 [mac80211] [ 135.900638] [] dev_hard_start_xmit+0x249/0x3d0 [ 135.900642] [] sch_direct_xmit+0xfc/0x220 [ 135.900647] [] __qdisc_run+0x103/0x1a0 [ 135.900651] [] net_tx_action+0xe0/0x240 [ 135.900652] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900660] [] __do_softirq+0x101/0x290 [ 135.900664] [] run_ksoftirqd+0x28/0x50 [ 135.900669] [] smpboot_thread_fn+0x105/0x160 [ 135.900671] [] ? sort_range+0x30/0x30 [ 135.900673] [] kthread+0xd8/0xf0 [ 135.900674] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900677] [] ret_from_fork+0x3f/0x70 [ 135.900679] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900680] ---[ end trace 492e0702110b49d9 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rohit 2164 F pulseaudio /dev/snd/controlC0: rohit 2164 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 31 20:09:30 2016 HibernationDevice: RESUME=UUID=11a54c6b-4b7c-4d4e-b084-6d6916d01e1a InstallationDate: Installed on 2015-08-28 (429 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=fdd19df7-3b7b-479a-8caa-d9e7f62e0641 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard b
[Kernel-packages] [Bug 1638025] Re: MT7601U module crashes with 4.4.0.45 Kernel
+0x30/0x30 [ 135.900673] [] kthread+0xd8/0xf0 [ 135.900674] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900677] [] ret_from_fork+0x3f/0x70 [ 135.900679] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900680] ---[ end trace 492e0702110b49d9 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rohit 2164 F pulseaudio /dev/snd/controlC0: rohit 2164 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 31 20:09:30 2016 HibernationDevice: RESUME=UUID=11a54c6b-4b7c-4d4e-b084-6d6916d01e1a InstallationDate: Installed on 2015-08-28 (429 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=fdd19df7-3b7b-479a-8caa-d9e7f62e0641 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S2PH dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd11/10/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2PH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2PH:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-S2PH dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638025/+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 1638025] Re: MT7601U module crashes with 4.4.0.45 Kernel
There is some issue with mt7601u module available with default kernel post 16.04. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1638025 Title: MT7601U module crashes with 4.4.0.45 Kernel Status in linux package in Ubuntu: Confirmed Bug description: There are frequent crash seen with MT7601U module with latest kernel 4.4.0.45. [ 135.900428] [ cut here ] [ 135.900434] WARNING: CPU: 1 PID: 13 at /build/linux-kOWph6/linux-4.4.0/drivers/net/wireless/mediatek/mt7601u/dma.c:291 mt7601u_dma_enqueue_tx+0x26b/0x2a0 [mt7601u]() [ 135.900435] Modules linked in: [ 135.900436] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900437] ip6table_filter [ 135.900439] ip6_tables iptable_filter [ 135.900440] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900441] ip_tables x_tables drbg ansi_cprng ctr ccm arc4 mt7601u mac80211 cfg80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp nls_iso8859_1 kvm_intel kvm rndis_host cdc_ether irqbypass usbnet snd_hda_codec_hdmi snd_hda_codec_realtek crct10dif_pclmul crc32_pclmul snd_hda_codec_generic snd_hda_intel aesni_intel aes_x86_64 joydev snd_hda_codec input_leds lrw snd_hda_core gf128mul snd_hwdep glue_helper snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ablk_helper snd_timer snd serio_raw soundcore cryptd mei_me mei shpchp lpc_ich mac_hid tpm_infineon 8250_fintek parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid i915 i2c_algo_bit [ 135.900472] drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops drm ahci r8169 libahci mii video fjes [ 135.900478] CPU: 1 PID: 13 Comm: ksoftirqd/1 Tainted: GW 4.4.0-45-generic #66-Ubuntu [ 135.900479] Hardware name: Gigabyte Technology Co., Ltd. H81M-S2PH/H81M-S2PH, BIOS FC 11/10/2014 [ 135.900480] 0086 489d46bf 880215b3f970 813f1fe3 [ 135.900483] c04ec118 880215b3f9a8 81081212 [ 135.900485] 880035716858 880210e32898 0005 8800d0dc8d00 [ 135.900487] Call Trace: [ 135.900490] [] dump_stack+0x63/0x90 [ 135.900492] [] warn_slowpath_common+0x82/0xc0 [ 135.900494] [] warn_slowpath_null+0x1a/0x20 [ 135.900498] [] mt7601u_dma_enqueue_tx+0x26b/0x2a0 [mt7601u] [ 135.900511] [] ? minstrel_ht_get_rate+0x34/0x4c0 [mac80211] [ 135.900516] [] mt7601u_tx+0x223/0x3c0 [mt7601u] [ 135.900528] [] ? ieee80211_crypto_ccmp_encrypt+0x34/0x250 [mac80211] [ 135.900540] [] ieee80211_tx_frags+0x170/0x3b0 [mac80211] [ 135.900552] [] __ieee80211_tx+0x81/0x180 [mac80211] [ 135.900554] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900569] [] ieee80211_tx+0xdf/0x110 [mac80211] [ 135.900582] [] ieee80211_xmit+0x9b/0xf0 [mac80211] [ 135.900594] [] __ieee80211_subif_start_xmit+0x55b/0x790 [mac80211] [ 135.900598] [] ? csum_partial_ext+0x9/0x10 [ 135.900604] [] ? __skb_checksum+0x65/0x2d0 [ 135.900608] [] ? select_idle_sibling+0xef/0x120 [ 135.900613] [] ? kfree_skbmem+0x59/0x60 [ 135.900617] [] ? consume_skb+0x34/0x90 [ 135.900622] [] ? packet_rcv+0x44/0x440 [ 135.900634] [] ieee80211_subif_start_xmit+0x10/0x20 [mac80211] [ 135.900638] [] dev_hard_start_xmit+0x249/0x3d0 [ 135.900642] [] sch_direct_xmit+0xfc/0x220 [ 135.900647] [] __qdisc_run+0x103/0x1a0 [ 135.900651] [] net_tx_action+0xe0/0x240 [ 135.900652] systemd-journald[256]: /dev/kmsg buffer overrun, some messages lost. [ 135.900660] [] __do_softirq+0x101/0x290 [ 135.900664] [] run_ksoftirqd+0x28/0x50 [ 135.900669] [] smpboot_thread_fn+0x105/0x160 [ 135.900671] [] ? sort_range+0x30/0x30 [ 135.900673] [] kthread+0xd8/0xf0 [ 135.900674] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900677] [] ret_from_fork+0x3f/0x70 [ 135.900679] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 135.900680] ---[ end trace 492e0702110b49d9 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rohit 2164 F pulseaudio /dev/snd/controlC0: rohit 2164 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 31 20:09:30 2016 HibernationDevice: RESUME=UUID=11a54c6b-4b7c-4d4e-b084-6d6916d01e1a InstallationDate: Installed on 2015-08-28 (429 days ago) InstallationMe
[Kernel-packages] [Bug 1941673] [NEW] keyboard and touchpad crashes after opening lid
Public bug reported: I have set the configuration s.t If I close the lid my laptop will suspend. But after resume from suspend keyboard and touchpad do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:42:51 2021 InstallationDate: Installed on 2021-07-19 (37 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941673 Title: keyboard and touchpad crashes after opening lid Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I have set the configuration s.t If I close the lid my laptop will suspend. But after resume from suspend keyboard and touchpad do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:42:51 2021 InstallationDate: Installed on 2021-07-19 (37 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1941673/+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 1992226] [NEW] Touchpad is not working at all.
Public bug reported: I have tried few commands like "cat /proc/bus/input/devices" and "xinput list" but my touchpad is not being recognized at all. As per documentation, it looks like kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-39-generic 5.15.0-39.42 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohit 3259 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 14:08:17 2022 InstallationDate: Installed on 2022-07-04 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=d399d805-ac2d-4691-bf94-5d2f59b10c12 ro quiet splash i8042.nomux i8024.noloop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2020 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrDKCN49WW:bd10/26/2020:br1.49:efr1.49:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:skuLENOVO_MT_82C5_BU_idea_FM_V15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1992226 Title: Touchpad is not working at all. Status in linux package in Ubuntu: New Bug description: I have tried few commands like "cat /proc/bus/input/devices" and "xinput list" but my touchpad is not being recognized at all. As per documentation, it looks like kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-39-generic 5.15.0-39.42 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: rohit 3259 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 14:08:17 2022 InstallationDate: Installed on 2022-07-04 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=d399d805-ac2d-4691-bf94-5d2f59b10c12 ro quiet splash i8042.nomux i8024.noloop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2020 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrDKCN49WW:bd10/26/2020:br1.49:efr1.49:svnLENOVO:pn82C5:pvrLenovoV15-IIL:
[Kernel-packages] [Bug 1915276] Re: [Lenovo V15-IIL] Touchpad not working
@Alex tried with hwe kernel but issue still persists. tried installing oem kernel, getting below error sudo apt install linux-oem-20.04b [sudo] password for rohit: Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-oem-20.04b E: Couldn't find any package by glob 'linux-oem-20.04b' -- 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/1915276 Title: [Lenovo V15-IIL] Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I have recently switched to Ubuntu from Windows 10 but during and after the installation the touchpad is unresponsive at all. I have tried almost all the things from google but nothing works. I hope this issue might get resolved soon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neutrino 1440 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:16:29 2021 InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:1135 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=e14254b4-ac0f-4e72-8e11-a450ac37103c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-10 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915276/+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 1989010] [NEW] trackpad not working
Public bug reported: The trackpad is not working on ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: confused 1570 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 21:02:21 2022 InstallationDate: Installed on 2022-08-29 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:118d Syntek Integrated Camera Bus 001 Device 002: ID 04ca:00a8 Lite-On Technology Corp. Dell Wireless Mouse WM118 Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO INVALID ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=f36b7f07-3ab0-4d61-94f8-6fbbc1ea9e73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:br1.40:efr1.40:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnINVALID:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrINVALID:skuLENOVO_BI_IDEAPADEM_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPADEM_BU_idea_FM_IDEAPAD dmi.product.version: INVALID dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "result of cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1989010/+attachment/5614425/+files/devices -- 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/1989010 Title: trackpad not working Status in linux package in Ubuntu: New Bug description: The trackpad is not working on ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: confused 1570 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 21:02:21 2022 InstallationDate: Installed on 2022-08-29 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:118d Syntek Integrated Camera Bus 001 Device 002: ID 04ca:00a8 Lite-On Technology Corp. Dell Wireless Mouse WM118 Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO INVALID ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=f36b7f07-3ab0-4d61-94f8-6fbbc1ea9e73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:br1.40:efr1.40:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnINVALID:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrINVALID:skuLENOVO_BI_IDEAPADEM_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPADEM_BU_idea_FM_IDEAPAD dmi.product.version: INVAL
