[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
The output of lspci | grep Network: 01:00.0 Network controller: MEDIATEK Corp. Device 0616 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
lspci | grep -i mt79 doesn`t return anything in my case :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I installed https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28/+build/27759768/+files/linux- firmware_20220329.git681281e4-0ubuntu3.28_all.deb via dpkg and rebooted, but I still have the old firmware. Do I need to install it via QApt? And if so, why is that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
That might be the case, from my previous attempts to manually update it. Could you tell me how to remove them, without breaking anything? I'd really appreciate it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I enabled jammy-proposed and installed the firmware update, but unfortunately the update still didn’t load as indicated by the build times. I tried re-installing, but got this output linux-firmware is already the newest version (20220329.git681281e4-0ubuntu3.28). Selected version '20220329.git681281e4-0ubuntu3.28' (Ubuntu:22.04/jammy-proposed [all]) for 'linux-firmware' I don’t really understand, why I still don’t have the updated firmware. Does anyone here have an idea or can try installing the firmware update via jammy-proposed themselves? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
The speaker works with linux-oem-6.1-6.1.0-1023 firmware-sof-signed 2.0-1ubuntu4.2 on https://certification.canonical.com/hardware/202309-32142/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 1924298] Re: accept returns duplicate endpoints under load
The issue has been reproduced on fully patched versions of Ubuntu 22.04 as well. nov. 30 06:42:04 sd-170774 tomcat9[395629]: java.io.IOException: Duplicate accept detected. This is a known OS bug. Please consider reporting that you are affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298 nov. 30 06:42:04 sd-170774 tomcat9[395629]: at org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:548) nov. 30 06:42:04 sd-170774 tomcat9[395629]: at org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:78) nov. 30 06:42:04 sd-170774 tomcat9[395629]: at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:129) nov. 30 06:42:04 sd-170774 tomcat9[395629]: at java.lang.Thread.run(Thread.java:750) -- 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/1924298 Title: accept returns duplicate endpoints under load Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: When accepting client connections under load, duplicate endpoints may be returned. These endpoints will have different (usually sequential) file descriptors but will refer to the same connection (same server IP, same server port, same client IP, same client port). Both copies of the endpoint appear to be functional. Reproduction requires: - compilation of the attached server.c program - wrk (https://github.com/wg/wrk) to generate load The steps to reproduce are: - run 'server' application in one console window - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency --timeout 1s http://localhost:/post; done' in a second console window - run the same command in a third window to generate concurrent load You may need to run additional instance of the wrk command in multiple windows to trigger the issue. When the problem occurs the server executable will exit and print some debugging info. e.g.: accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient = 232 This indicates that the sockets with file descriptors 233 and 232 are duplicates. The issue has been reproduced on fully patched versions of Ubuntu 20.04 and 18.04. Other versions have not been tested. This issue was originally observed in Java and was reported against the Spring Framework: https://github.com/spring-projects/spring-framework/issues/26434 Investigation from the Spring team and the Apache Tomcat team identified that it appeared to be a JDK issue: https://bugs.openjdk.java.net/browse/JDK-8263243 Further research from the JDK team determined that the issue was at the OS level. Hence this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 12:52:53 2021 HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d InstallationDate: Installed on 2017-02-02 (1532 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. docker0 no wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/ubuntu--vg-root ro text RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago) dmi.bios.date: 06/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22 dmi.board.asset.tag: Default string dmi.board.name: X99-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1924298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
> Having the same problem, running on a Dell XPS 13 9310. https://www.dell.com/community/XPS/XPS-13-9310-Ubuntu-deep-sleep- missing/m-p/8056343/highlight/true#M91204 says that deep sleep isn't supported on the 9310 so what you describe is actually expected supposedly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics
Computer became unusable. Takes forever to start. Fails to shutdown. In the console (Ctrl+alt+f2) reports kernel panic. Ryzen 3500U. -- 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/1956396 Title: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics Status in linux package in Ubuntu: Confirmed Bug description: 5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3) Had been using the 5.13 HWE kernel for months with no problems. Today the kernel and linux-firmware updated. 5.13.0-23 kernel now takes about 2 minutes to boot to the login screen. Normal boot time is 8 seconds. During that time the pc is frozen with only a _ underline cursor that doesn't flash. Can't change terminals with Ctrl+Alt+F1, etc. Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure the problem is in the kernel and not linux-firmware. System information (while using 5.11 kernel) CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59089 Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330 Graphics: Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-44-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 direct render: Yes Forums threads about it: https://ubuntuforums.org/showthread.php?t=2470574 https://forums.linuxmint.com/viewtopic.php?f=46=364729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+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 1916314] Re: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot
(It took 30 seconds on the next boot) -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468223/+files/ProcModules.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468226/+files/UdevDb.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468228/+files/acpidump.txt ** 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468221/+files/ProcEnviron.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468222/+files/ProcInterrupts.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468225/+files/RfKill.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468224/+files/PulseList.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Re: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot
In the apport-collected CurrentDmesg.txt, the keyboard is detected at: [ 11.664651] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input44 That's sooner than it usually takes! -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468227/+files/WifiSyslog.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468219/+files/ProcCpuinfo.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468220/+files/ProcCpuinfoMinimal.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468218/+files/PaInfo.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468217/+files/Lsusb-v.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468214/+files/Lspci-vt.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468210/+files/CRDA.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468216/+files/Lsusb-t.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468211/+files/CurrentDmesg.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468215/+files/Lsusb.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468212/+files/IwConfig.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468213/+files/Lspci.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] Re: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot
apport information ** Tags added: apport-collected groovy ** Description changed: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: maxb 1195 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-02-03 (23 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: HP HP Spectre x360 Convertible 14-ea0xxx + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-44-generic N/A + linux-backports-modules-5.8.0-44-generic N/A + linux-firmware1.190.3 + Tags: groovy + Uname: Linux 5.8.0-44-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/13/2021 + dmi.bios.release: 15.9 + dmi.bios.vendor: AMI + dmi.bios.version: F.09 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 87F7 + dmi.board.vendor: HP + dmi.board.version: 40.43 + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 40.43 + dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Spectre + dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx + dmi.product.sku: 2G2C7EA#ABU + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1916314/+attachment/5468209/+files/AlsaInfo.txt -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Confirmed Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-03 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1916314] Re: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot
> Have you compiled kernel with that patch? No, I haven't. The workaround of setting i8042.nopnp is satisfactory for me, and the patch creator has done a thorough write up of the problem. My objective in filing this bug is to raise awareness that the current version of Ubuntu has this problem - on fairly major hardware from a mainstream vendor - so that other people searching the bug tracker for it can more easily find out. Or, that it might draw the attention of Ubuntu kernel maintainers for possible inclusion as a SAUCE patch whilst waiting for upstream inclusion. Or, getting a bit hopeful here, that someone at Canonical could get someone at HP to fix their "quirky" i8042 emulation. -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: Incomplete Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1916314] [NEW] HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot
Public bug reported: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html + + + A workaround is to add i8042.nopnp to the kernel command line -- 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/1916314 Title: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot Status in linux package in Ubuntu: New Bug description: On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is inoperable for ~30-60 seconds after system boot. Kernel logging reveals that it did not detect the keyboard during this time. An analysis of this and a patch can be found at: https://www.spinics.net/lists/linux-input/msg71677.html A workaround is to add i8042.nopnp to the kernel command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916314/+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 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
I also have this exact model of laptop. I have installed kernel 5.11 from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.11/ Following a cold boot to Ubuntu, sound can be made to work via the workaround GPIO commands detailed in https://bugzilla.kernel.org/show_bug.cgi?id=210633#c13 The related patch to teach the kernel to do the necessary GPIO itself is https://patchwork.kernel.org/project/alsa- devel/patch/20210215082540.4520-1-ti...@suse.de/ ** Bug watch added: Linux Kernel Bug Tracker #210633 https://bugzilla.kernel.org/show_bug.cgi?id=210633 -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1481 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-04 (2
[Kernel-packages] [Bug 1913901] [NEW] package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.1
Public bug reported: just starting up. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 26 20:26:44 2021 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.80.02-0ubuntu0.20.04.3 Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) over (450.80.02-0ubuntu0.20.04.3) ... dpkg: error processing archive /tmp/apt-dpkg-install-J9wJuZ/13-libnvidia-common-450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-03-20 (316 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450-server Title: package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 UpgradeStatus: Upgraded to focal on 2020-10-25 (97 days ago) ** Affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1913901 Title: package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: just starting up. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 26 20:26:44 2021 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.80.02-0ubuntu0.20.04.3 Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) over (450.80.02-0ubuntu0.20.04.3) ... dpkg: error processing archive /tmp/apt-dpkg-install-J9wJuZ/13-libnvidia-common-450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-03-20 (316 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450-server Title: package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', which is also in package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 UpgradeStatus: Upgraded to focal on 2020-10-25 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1913901/+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 1851068] Re: laptop does not wakeup after suspend (when lid off). Need to had reset
same bug with the last kernel released 5.4.0-48-generic bug occurs with an update one month ago -- 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/1851068 Title: laptop does not wakeup after suspend (when lid off). Need to had reset Status in linux package in Ubuntu: Confirmed Bug description: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My laptop is hp spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dror 1529 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-31 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic root=UUID=ad8d697c-17a2-4ab1-97ac-a1f665546354 ro acpi_osi=! "acpi_osi=Windows 2015" nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-21-generic N/A linux-backports-modules-5.3.0-21-generic N/A linux-firmware1.183.1 Tags: wayland-session eoan Uname: Linux 5.3.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863E dmi.board.vendor: HP dmi.board.version: 53.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd10/14/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863E:rvr53.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV29AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851068/+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 1851068] Re: laptop does not wakeup after suspend (when lid off). Need to had reset
after systemctl suspend, during wakeup, fsck with messages like EXT4-fs error (device nvme0n1p2) Aborting journal on device nvme0n1p3-8 Buffer I/O error on dev nvme0n1p3, logical block 59801600, lost sync page write -- 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/1851068 Title: laptop does not wakeup after suspend (when lid off). Need to had reset Status in linux package in Ubuntu: Confirmed Bug description: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My laptop is hp spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dror 1529 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-31 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic root=UUID=ad8d697c-17a2-4ab1-97ac-a1f665546354 ro acpi_osi=! "acpi_osi=Windows 2015" nouveau.modeset=0 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-21-generic N/A linux-backports-modules-5.3.0-21-generic N/A linux-firmware1.183.1 Tags: wayland-session eoan Uname: Linux 5.3.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2019 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863E dmi.board.vendor: HP dmi.board.version: 53.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd10/14/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863E:rvr53.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV29AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851068/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
+1 -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1880835] Re: pulse audio hangs in kernel call
Taking after csita I unplugged/replugged all my external audio devices and restarted pulseaudio and alsa-mixer. I found the below error in journalctl: Jun 27 09:15:37 hostname pulseaudio[3735]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-N-SIA_KJ- USB_HEASET-00" card_name="alsa_card.usb-N-SIA_KJ-USB_HEASET-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties ="module-udev-detect.discovered=1""): initialization failed. This is a usb headset. When unplugging and leaving unplugged after reboot everything works. The failure to load the the module for the USB headset was for some reason leaving pulseaudio blocked on IO in a D state. I use audio via HDMI output from my Nvidia card. I have Nvidia driver 440 installed on my system, but I do not use the Nvidia driver. I still use nouveau. -- 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions:
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
My system has hit the same bug and I do not use firewire. I have not upgraded to mainline kernel. The power cycling work arounds above do not mitigate the issue for me. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" $ uname -a Linux hostname 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ pactl info Connection failure: Connection refused pa_context_connect() failed: Connection refused $ ps aux | grep pulse | grep -v grep username12895 17.0 0.0 100788 10908 ?D] usb_start_wait_urb+0x8f/0x180 [<0>] usb_control_msg+0xe3/0x140 [<0>] snd_usb_ctl_msg+0xe3/0x190 [snd_usb_audio] [<0>] snd_usb_init_sample_rate+0x235/0x320 [snd_usb_audio] [<0>] snd_usb_pcm_prepare+0x159/0x460 [snd_usb_audio] [<0>] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [<0>] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [<0>] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [<0>] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [<0>] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [<0>] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [<0>] do_vfs_ioctl+0x407/0x670 [<0>] ksys_ioctl+0x67/0x90 [<0>] __x64_sys_ioctl+0x1a/0x20 [<0>] do_syscall_64+0x57/0x190 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 The stack frames line up w/ the above. $ journalctl -f | grep pulse # a selection of the output Jun 27 09:38:50 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:38:50 hostname systemd[2373]: pulseaudio.service: Killing process 12140 (pulseaudio) with signal SIGKILL. Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:38:56 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jun 27 09:38:56 hostname pulseaudio[12895]: Stale PID file, overwriting. Jun 27 09:40:26 hostname systemd[2373]: pulseaudio.service: start operation timed out. Terminating. Jun 27 09:41:56 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:41:56 hostname systemd[2373]: pulseaudio.service: Killing process 12895 (pulseaudio) with signal SIGKILL. Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:42:02 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 6. Jun 27 09:42:03 hostname pulseaudio[13050]: Stale PID file, overwriting. Jun 27 09:43:33 hostname systemd[2373]: pulseaudio.service: start operation timed out. Terminating. Jun 27 09:45:03 hostname systemd[2373]: pulseaudio.service: State 'stop-sigterm' timed out. Killing. Jun 27 09:45:03 hostname systemd[2373]: pulseaudio.service: Killing process 13050 (pulseaudio) with signal SIGKILL. Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Main process exited, code=killed, status=9/KILL Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Failed with result 'timeout'. Jun 27 09:45:10 hostname systemd[2373]: pulseaudio.service: Scheduled restart job, restart counter is at 7. -- 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ?
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
sudo prime-select intel fixed it for my Acer Nitro 5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1775717 Title: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and GPU fans suddenly go full throttle. It doesn't seem to depend on temperature, could happen when 32 °C reported, sometimes the laptop can work for day or two without this issue, but eventually it happens. The only way to stop fans is to power off the laptop, power on (fans go 100% at this point again), power off during BIOS splash screen and power on again. Seems to happen more often after waking up from a sleep. Things tried: Upgrading BIOS to latest available on ASUS site to the date of writing. No change. asus-fan kernel module (https://github.com/daringer/asus-fan). Detects both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but does not seem to control it and does not prevent going full throttle. 4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the issue. Userspace fan control software (https://github.com/hirschmann/nbfc). Can control speed of both fans to the point where they go full throttle, after that has no effect on them. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: whale 3068 F pulseaudio /dev/snd/controlC0: whale 3068 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969 InstallationDate: Installed on 2014-10-20 (1333 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac (20140722.2) MachineType: ASUSTeK COMPUTER INC. G752VT NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty video _MarkForUpload: True dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VT.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G752VT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+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 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
I can confirm that booting without "quiet splash" in the grub config eliminates the problem. -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5371999/+files/IwConfig.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372011/+files/UdevDb.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372003/+files/Lsusb-t.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372012/+files/WifiSyslog.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] apport information
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1804 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-30 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire VN7-592G Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=ab475c17-6be6-426b-97b2-179a498b8a14 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.name: Aspire VN7-592G dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd10/06/2016:svnAcer:pnAspireVN7-592G:pvrV1.12:rvnAcer:rnAspireVN7-592G:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: SKL dmi.product.name: Aspire VN7-592G dmi.product.sku: Aspire VN7-592G_1039_1.12 dmi.product.version: V1.12 dmi.sys.vendor: Acer -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372010/+files/RfKill.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5371998/+files/CurrentDmesg.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
Same here on Acer Nitro BE with intel + Nvidia Graphics Mesa Intel® HD Graphics 530 (SKL GT2) NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2) ** Tags added: apport-collected -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372009/+files/PulseList.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372006/+files/ProcCpuinfoMinimal.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372008/+files/ProcModules.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372002/+files/Lsusb.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372001/+files/Lspci-vt.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372005/+files/ProcCpuinfo.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5371996/+files/AlsaInfo.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372004/+files/Lsusb-v.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372000/+files/Lspci.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5372007/+files/ProcInterrupts.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1874194] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1874194/+attachment/5371997/+files/CRDA.txt -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1870946] Re: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 [8086:2723] subsystem [8086:4080]
hmm, it was "off" in the settings. So I tried turning it on and connecting to my bluetooth speaker to see what would happen, and the dmesg output looks like a mess (attached). The interface says the device is connected but it doesn't show up in pavucontrol. I'll try version 50 of the driver later today and report back On Tue, Apr 7, 2020, at 5:59 AM, You-Sheng Yang wrote: > I also noticed in your WifiSyslog.txt it has: > > kernel: Bluetooth: hci0: command 0xfc09 tx timeout > > Does this Dell 7740 have Bluetooth functioning at all time? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870946 > > Title: > iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 > [8086:2723] subsystem [8086:4080] > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > 0 > > I'm running an up-to-date version of the dev branch and have had a > problem since I first installed it. > > I'm on a new Dell Precision 7740, with: > > Intel i9-9880H > > Radeon Pro WX 3200 > > and network card is: > > Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver > > I'm getting a bunch of problems. Packet loss varies from 15%-35%, > often I can't load anything when I'm on wifi. Also sometimes `ping` > errors out with: > > From 192.168.1.247 icmp_seq=138 Destination Host Unreachable > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu21 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: max8466 F pulseaudio >/dev/snd/pcmC0D0p: max8466 F...m pulseaudio >/dev/snd/controlC1: max8466 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 5 11:57:32 2020 > InstallationDate: Installed on 2020-03-13 (23 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) > IwConfig: >wlp112s0 no wireless extensions. > >eno1 no wireless extensions. > >lono wireless extensions. > MachineType: Dell Inc. Precision 7740 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/fish > ProcFB: >0 i915drmfb >1 amdgpudrmfb > ProcKernelCmdLine: > BOOT_IMAGE=/BOOT/ubuntu_igsmls@/vmlinuz-5.4.0-21-generic > root=ZFS=rpool/ROOT/ubuntu_igsmls ro quiet splash vt.handoff=1 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-21-generic N/A >linux-backports-modules-5.4.0-21-generic N/A >linux-firmware1.187 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/10/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.6.0 > dmi.board.name: 0FRKPX > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.6.0:bd12/10/2019:svnDellInc.:pnPrecision7740:pvr:rvnDellInc.:rn0FRKPX:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Precision > dmi.product.name: Precision 7740 > dmi.product.sku: 0927 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870946/+subscriptions > ** Attachment added: "dmesg | grep iwlwifi.log" https://bugs.launchpad.net/bugs/1870946/+attachment/5348842/+files/dmesg%20%7C%20grep%20iwlwifi.log -- 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/1870946 Title: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 [8086:2723] subsystem [8086:4080] Status in linux package in Ubuntu: Incomplete Bug description: 0 I'm running an up-to-date version of the dev branch and have had a problem since I first installed it. I'm on a new Dell Precision 7740, with: Intel i9-9880H Radeon Pro WX 3200 and network card is: Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver I'm getting a bunch of problems. Packet loss varies from 15%-35%, often I can't load anything when I'm on wifi. Also sometimes `ping` errors out with: From 192.168.1.247 icmp_seq=138 Destination Host Unreachable ProblemType: Bug Di
Re: [Kernel-packages] [Bug 1870946] Re: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200
Hey, Followed your steps and still seeing the problem, but in case this is a clue: My wifi seemed to be working normally at first. After about two minutes of ping acting normally and browsing I tried doing `sudo service network-manager restart` to see if the problem came back and it indeed returned right away. You can see where I ran the restart command in the timestamps in the attached dmesg output. -Max On Sun, Apr 5, 2020, at 12:42 PM, You-Sheng Yang wrote: > It seems you're suffering from wifi firmware crash and the hardware is > resetting itself occasionally. Please try: > > 1. backup your /lib/firmware > 2. Clone > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ > to replace /lib/firmware > 3. Shutdown completely for a minute and reboot > > If this works for you, that means the WiFi firmware should be updated. > Focal, as a dev branch, should have almost always the latest fw, but > let's see. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870946 > > Title: > iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > 0 > > I'm running an up-to-date version of the dev branch and have had a > problem since I first installed it. > > I'm on a new Dell Precision 7740, with: > > Intel i9-9880H > > Radeon Pro WX 3200 > > and network card is: > > Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver > > I'm getting a bunch of problems. Packet loss varies from 15%-35%, > often I can't load anything when I'm on wifi. Also sometimes `ping` > errors out with: > > From 192.168.1.247 icmp_seq=138 Destination Host Unreachable > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu21 > Architecture: amd64 > AudioDevicesInUse: >USER PID ACCESS COMMAND >/dev/snd/controlC0: max8466 F pulseaudio >/dev/snd/pcmC0D0p: max8466 F...m pulseaudio >/dev/snd/controlC1: max8466 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 5 11:57:32 2020 > InstallationDate: Installed on 2020-03-13 (23 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) > IwConfig: >wlp112s0 no wireless extensions. > >eno1 no wireless extensions. > >lono wireless extensions. > MachineType: Dell Inc. Precision 7740 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/fish > ProcFB: >0 i915drmfb >1 amdgpudrmfb > ProcKernelCmdLine: > BOOT_IMAGE=/BOOT/ubuntu_igsmls@/vmlinuz-5.4.0-21-generic > root=ZFS=rpool/ROOT/ubuntu_igsmls ro quiet splash vt.handoff=1 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-21-generic N/A >linux-backports-modules-5.4.0-21-generic N/A >linux-firmware1.187 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/10/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.6.0 > dmi.board.name: 0FRKPX > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.6.0:bd12/10/2019:svnDellInc.:pnPrecision7740:pvr:rvnDellInc.:rn0FRKPX:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Precision > dmi.product.name: Precision 7740 > dmi.product.sku: 0927 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870946/+subscriptions > ** Attachment added: "dmesg | grep iwlwifi.log" https://bugs.launchpad.net/bugs/1870946/+attachment/5347415/+files/dmesg%20%7C%20grep%20iwlwifi.log -- 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/1870946 Title: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 Status in linux package in Ubuntu: Confirmed Bug description: 0 I'm running an up-to-date version of the dev branch and have had a problem since I first installed it. I'm on a new Dell Precision 7740, with: Intel i9-9880H Radeon Pr
[Kernel-packages] [Bug 1870946] [NEW] iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200
Public bug reported: 0 I'm running an up-to-date version of the dev branch and have had a problem since I first installed it. I'm on a new Dell Precision 7740, with: Intel i9-9880H Radeon Pro WX 3200 and network card is: Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver I'm getting a bunch of problems. Packet loss varies from 15%-35%, often I can't load anything when I'm on wifi. Also sometimes `ping` errors out with: >From 192.168.1.247 icmp_seq=138 Destination Host Unreachable ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max8466 F pulseaudio /dev/snd/pcmC0D0p: max8466 F...m pulseaudio /dev/snd/controlC1: max8466 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 11:57:32 2020 InstallationDate: Installed on 2020-03-13 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) IwConfig: wlp112s0 no wireless extensions. eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Precision 7740 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_igsmls@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_igsmls ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0FRKPX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd12/10/2019:svnDellInc.:pnPrecision7740:pvr:rvnDellInc.:rn0FRKPX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7740 dmi.product.sku: 0927 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dumps_for_bug_report.tar.xz" https://bugs.launchpad.net/bugs/1870946/+attachment/5347158/+files/dumps_for_bug_report.tar.xz -- 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/1870946 Title: iwlwifi breaking on dell precision 7740 with Intel Wi-Fi 6 AX200 Status in linux package in Ubuntu: New Bug description: 0 I'm running an up-to-date version of the dev branch and have had a problem since I first installed it. I'm on a new Dell Precision 7740, with: Intel i9-9880H Radeon Pro WX 3200 and network card is: Intel Wi-Fi 6 AX200 2x2 .11ax 160MHz + Bluetooth 5.0 Driver I'm getting a bunch of problems. Packet loss varies from 15%-35%, often I can't load anything when I'm on wifi. Also sometimes `ping` errors out with: From 192.168.1.247 icmp_seq=138 Destination Host Unreachable ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max8466 F pulseaudio /dev/snd/pcmC0D0p: max8466 F...m pulseaudio /dev/snd/controlC1: max8466 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 11:57:32 2020 InstallationDate: Installed on 2020-03-13 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) IwConfig: wlp112s0 no wireless extensions. eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Precision 7740 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_igsmls@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_igsmls ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
I have this big with 18.04 LTS and kernel 5.3.0-40-generic ** Attachment added: "file /sys/class/drm/card0/error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/+attachment/5330656/+files/error -- 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/1861395 Title: system hang: i915 Resetting rcs0 for hang on rcs0 Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Invalid Status in linux source package in Focal: Incomplete Bug description: System hangs, unknown cause, When this happens, the mouse pointer still moves, but I can't do anything else with the keys or clicking in the UI. Only recover I have found is a hard power-off Last bit of kern.log below: Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required to analyze GPU hangs, so please always attach it. Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to /sys/class/drm/card0/error Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting chip for hang on rcs0 Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks suppressed Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0 ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000] Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 7d 8f 00 Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting rcs0 for hang on rcs0 Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 12:51:24 2020 InstallationDate: Installed on 2018-06-18 (591 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb 115653 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-06-18 (604 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics
[Kernel-packages] [Bug 1863752] Re: Removal of linux-image-5.3.0-29-generic fails
It's the GRUB config file that was created by the installer then modified by subsequent package updates (file has not been manually edited). grub.cfg.new file attached. ** Attachment added: "grub.cfg.new" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863752/+attachment/5329550/+files/grub.cfg.new -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863752 Title: Removal of linux-image-5.3.0-29-generic fails Status in linux package in Ubuntu: Incomplete Bug description: Attempting to update the kernel from linux-image-5.3.0-29-generic to 5.3.0-40-generic on a 19.10 system with default ZFS root and boot keeps failing. The latter has installed (for some value of install) but the former can't be removed and the system is left running that older kernel. Possibly due to some issue with setting up the next boot image under ZFS? root@foo:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED linux-image-5.3.0-29-generic 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 2 not fully installed or removed. After this operation, 11.4 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 228252 files and directories currently installed.) Removing linux-image-5.3.0-29-generic (5.3.0-29.31) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.3.0-29-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.elf Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sdb7 failed: Device or resource busy Command failed. Found Debian GNU/Linux 10 (buster) on /dev/sdc2 error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 178 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-5.3.0-29-generic (--remove): installed linux-image-5.3.0-29-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-5.3.0-29-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) root@foo:~# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 root@foo:~# apt-cache policy linux-image-5.3.0-29-generic linux-image-5.3.0-29-generic: Installed: 5.3.0-29.31 Candidate: 5.3.0-29.31 Version table: *** 5.3.0-29.31 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# apt-cache policy linux-image-5.3.0-40-generic linux-image-5.3.0-40-generic: Installed: 5.3.0-40.32 Candidate: 5.3.0-40.32 Version table: *** 5.3.0-40.32 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# uname -a Linux foo 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with
[Kernel-packages] [Bug 1863752] [NEW] Removal of linux-image-5.3.0-29-generic fails
Public bug reported: Attempting to update the kernel from linux-image-5.3.0-29-generic to 5.3.0-40-generic on a 19.10 system with default ZFS root and boot keeps failing. The latter has installed (for some value of install) but the former can't be removed and the system is left running that older kernel. Possibly due to some issue with setting up the next boot image under ZFS? root@foo:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED linux-image-5.3.0-29-generic 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 2 not fully installed or removed. After this operation, 11.4 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 228252 files and directories currently installed.) Removing linux-image-5.3.0-29-generic (5.3.0-29.31) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.3.0-29-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.elf Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sdb7 failed: Device or resource busy Command failed. Found Debian GNU/Linux 10 (buster) on /dev/sdc2 error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 178 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-5.3.0-29-generic (--remove): installed linux-image-5.3.0-29-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-5.3.0-29-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) root@foo:~# lsb_release -rd Description:Ubuntu 19.10 Release:19.10 root@foo:~# apt-cache policy linux-image-5.3.0-29-generic linux-image-5.3.0-29-generic: Installed: 5.3.0-29.31 Candidate: 5.3.0-29.31 Version table: *** 5.3.0-29.31 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# apt-cache policy linux-image-5.3.0-40-generic linux-image-5.3.0-40-generic: Installed: 5.3.0-40.32 Candidate: 5.3.0-40.32 Version table: *** 5.3.0-40.32 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# uname -a Linux foo 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Feb 18 12:06:33 2020 InstallationDate: Installed on 2020-01-16 (32 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Z200 Workstation ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1863064] [NEW] package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Hang on install package ProblemType: Package DistroRelease: Ubuntu 19.10 Package: kexec-tools 1:2.0.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Feb 13 09:54:03 2020 ErrorMessage: installed kexec-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-12-11 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: kexec-tools Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863064 Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1 Status in kexec-tools package in Ubuntu: New Bug description: Hang on install package ProblemType: Package DistroRelease: Ubuntu 19.10 Package: kexec-tools 1:2.0.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Feb 13 09:54:03 2020 ErrorMessage: installed kexec-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-12-11 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: kexec-tools Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1863064/+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 1860306] [NEW] Linux kernel 5.3.0-26 breaks nvidia driver
Public bug reported: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description:Linux Mint 19.3 Tricia Release:19.3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: New Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+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 1847389] Re: Prevent bpool (or pools with /BOOT/) to be upgraded
How exactly does it break booting? I did a zpool upgrade bpool on two machines (one VM and one laptop) before reading this warning. Both seems to boot just fine after the upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded Status in zfs-linux package in Ubuntu: New Bug description: The bpool status is confusing. Should I upgrade the pool or is it on purpose that the bpool is like this. I do no like to see this warning after installing the system on ZFS from scratch. See screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I have a Lenovo E585 w/ a Ryzen 5 2500U. I'm having the same issues, horizontal screen tears, parts of a window showing up where they shouldn't. It's mostly on Firefox, but happens when I view PDFs as well. I'm getting different problems on Steam, there it's small colored squares that flash on and off. I'm also having a problem where every time I wake from sleep I get a black screen, not sure if related but maybe it is? I'm happy to upload lspci and dmesg info if that would help! -- 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/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Same Problem Dell XPS 15z Kernel: 4.18.0-22-generic OS: 18.04.02 Window manager: KDE Not using Nvidia blob drivers. Editing grub with "acpi=force reboot=pci" didn't help. Sometimes also partially freezes when using firefox (mouse dosen't move, ping command dosen't work, can't kill -9 firefox process) -- 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/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1829657] Re: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt
Whan starting 4.4.0-148 in recovery mode, this is the position where the system hangs. ** Attachment added: "IMG_20190519_165849066.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1829657/+attachment/5264839/+files/IMG_20190519_165849066.jpg -- 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/1829657 Title: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt Status in linux-signed package in Ubuntu: New Bug description: After the automatic update from 4.4.0-145 to 4.4.0-148 on a Thinkpad L460 the boot process hangs before any visible output and doesnt proceed from there. Changing back to 4.4.0-145 in the grub menu makes the boot proceed normally. > lspci -knn | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5051] Kernel driver in use: i915_bpo Kernel modules: i915_bpo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 19 16:36:06 2019 InstallationDate: Installed on 2016-11-04 (925 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed 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/1829657/+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 1829657] [NEW] Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt
Public bug reported: After the automatic update from 4.4.0-145 to 4.4.0-148 on a Thinkpad L460 the boot process hangs before any visible output and doesnt proceed from there. Changing back to 4.4.0-145 in the grub menu makes the boot proceed normally. > lspci -knn | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5051] Kernel driver in use: i915_bpo Kernel modules: i915_bpo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 19 16:36:06 2019 InstallationDate: Installed on 2016-11-04 (925 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1829657 Title: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt Status in linux-signed package in Ubuntu: New Bug description: After the automatic update from 4.4.0-145 to 4.4.0-148 on a Thinkpad L460 the boot process hangs before any visible output and doesnt proceed from there. Changing back to 4.4.0-145 in the grub menu makes the boot proceed normally. > lspci -knn | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5051] Kernel driver in use: i915_bpo Kernel modules: i915_bpo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 19 16:36:06 2019 InstallationDate: Installed on 2016-11-04 (925 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed 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/1829657/+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 1825699] Re: Touchpad not working after upgrade to 19.04
The kernel paramter "psmouse.elantech_smbus=0" did the trick. Thank you very much. No need to downgrade. -- 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/1825699 Title: Touchpad not working after upgrade to 19.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 the touch pad stopped working during the upgrade. cat /proc/bus/input/devices does not show any information about the Synaptics Touchpad. lsusb does show an entry: Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. synclient shows: Couldn't find synaptics properties. No synaptics driver loaded? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1990 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 08:32:38 2019 InstallationDate: Installed on 2019-04-10 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20LW0010GE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW0010GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET49W(1.26):bd09/25/2018:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW0010GE dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825699/+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 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
Thanks, partially helped. Ubuntu starts up normally, Kubuntu doesn’t run, which is a pity, because KDE I already like a lot more. I will stay at the Manjaro. -- 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
in attach ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+attachment/5257830/+files/lspci-vnvn.log -- 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1825699] [NEW] Touchpad not working after upgrade to 19.05
Public bug reported: After upgrading from 18.10 to 19.04 the touch pad stopped working during the upgrade. cat /proc/bus/input/devices does not show any information about the Synaptics Touchpad. lsusb does show an entry: Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. synclient shows: Couldn't find synaptics properties. No synaptics driver loaded? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1990 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 08:32:38 2019 InstallationDate: Installed on 2019-04-10 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20LW0010GE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW0010GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET49W(1.26):bd09/25/2018:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW0010GE dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco third-party-packages wayland-session ** Attachment added: "output of 'cat /usr/bus/input/devices'" https://bugs.launchpad.net/bugs/1825699/+attachment/5257443/+files/input_devices.txt -- 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/1825699 Title: Touchpad not working after upgrade to 19.05 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 the touch pad stopped working during the upgrade. cat /proc/bus/input/devices does not show any information about the Synaptics Touchpad. lsusb does show an entry: Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. synclient shows: Couldn't find synaptics properties. No synaptics driver loaded? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1990 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 08:32:38 2019 InstallationDate: Installed on 2019-04-10 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20LW0010GE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW0010GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET49W(1.26):bd09/25/2018:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW0010GE dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825699/+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 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
How to make them when loading live-usb, if you consider that the system does not boot and does not even give the command line interface? ** 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1825638] [NEW] Lenovo Legion Y530-15ICH does not start with live usb
Public bug reported: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: does legion lenovo not start y530-15ich -- 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/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+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 1817070] Re: Thunderbolt display not detected
@kaihengfeng Might this also be an USB issue? It seems to me that the root cause is somewhere in the order the USB-C to miniDP is detected. Does it make sense to post the issue there? -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] Re: Thunderbolt display not detected
Ok tried with new kernel but no change. I also figured out this is nit related to the dock. Behaves the same when I connect the adapter directly to thunderbolt port on the laptop. Order matters here as well. First adapter, then cable :). I will then create a bug for Intel graphics. -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] Re: Thunderbolt display not detected
I don't this is going to work, as this port is for data only and not for displays ** 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240691/+files/ProcModules.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240695/+files/WifiSyslog.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240684/+files/IwConfig.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240687/+files/ProcCpuinfo.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240686/+files/Lsusb.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240694/+files/UdevDb.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240693/+files/RfKill.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240692/+files/PulseList.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240690/+files/ProcInterrupts.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240689/+files/ProcEnviron.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240688/+files/ProcCpuinfoMinimal.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240685/+files/Lspci.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240683/+files/CurrentDmesg.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] Re: Thunderbolt display not detected
apport information ** Tags added: apport-collected tessa ** Description changed: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. - The second monitor is only detected, when I _first_ plug in the adapter - and _then_ plug in the the cable to the adapter. This also only works - when the system has booted _and_ I am logged in. I already disabled - thunderbolt security completely in UEFI. Once the monitor has been - detected it is also working during boot, when I restart the system. + The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: max1628 F...m pulseaudio + /dev/snd/controlC0: max1628 F pulseaudio + /dev/snd/controlC1: max1628 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.1 + HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 + InstallationDate: Installed on 2019-01-05 (47 days ago) + InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 + MachineType: Dell Inc. XPS 13 9370 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.173.3 + Tags: tessa + Uname: Linux 4.15.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/04/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.6.3 + dmi.board.name: 09DKKT + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9370 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240681/+files/AlsaInfo.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambasha
[Kernel-packages] [Bug 1817070] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1817070/+attachment/5240682/+files/CRDA.txt -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1817070] [NEW] Thunderbolt display not detected
Public bug reported: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "issue_logs" https://bugs.launchpad.net/bugs/1817070/+attachment/5240662/+files/display_issue_logs.zip -- 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/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Incomplete Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+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 1721987] Re: No sound from right audio channel
Hey, I tried the script solution together with the systemd service file. It works very nicely! I noticed that you also have to run the script when the device wakes from standby (e.g. closing-reopening the lid). For that to work, you have to add a few more targets to WantedBy (I just searched around, I did not test which ones you really need for that to work): suspend.target hibernate.target hybrid-sleep.target -- 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/1721987 Title: No sound from right audio channel Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: No audio comes out of the right speaker on the laptop. When playing a test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the right-channel audio is never heard (i.e., it does not get converted into mono and played through the left speaker). When plugging in headphones, audio is heard from both channels. In Windows, both speakers work, so it is not a physical problem with the speakers. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1127 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 12:58:01 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: HUAWEI HUAWEI MateBook X ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2017 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.12 dmi.board.name: HUAWEI MateBook X dmi.board.vendor: HUAWEI dmi.board.version: 2.0 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.modalias: dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr: dmi.product.family: HUAWEI MateBook dmi.product.name: HUAWEI MateBook X dmi.product.version: 2.0 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721987/+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