[Kernel-packages] [Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1906680): - CVE-2021-1052, CVE-2021-1053. * debian/templates/control.in: - Add support for libcuda-11.0-1, libcuda-11.1-1. * debian/templates/nvidia-compute-utils-flavour.nvidia-persistenced.service.in: Run persistenced.service before systemd-backlight@backlight:nvidia_0 (LP: #1885087). -- Alberto Milone Mon, 04 Jan 2021 15:18:07 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Groovy) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+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 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1906680): - CVE-2021-1052, CVE-2021-1053. * debian/templates/nvidia-compute-utils-flavour.nvidia-persistenced.service.in: Run persistenced.service before systemd-backlight@backlight:nvidia_0 (LP: #1885087). -- Alberto Milone Mon, 04 Jan 2021 16:11:01 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+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 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1906680): - CVE-2021-1052, CVE-2021-1053. * debian/templates/nvidia-compute-utils-flavour.nvidia-persistenced.service.in: Run persistenced.service before systemd-backlight@backlight:nvidia_0 (LP: #1885087). -- Alberto Milone Mon, 04 Jan 2021 15:47:43 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+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 1910697] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1910697/+attachment/5450628/+files/acpidump.txt
** Also affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: bcmwl (Ubuntu)
** Also affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910697
Title:
incapability with broadcom wifi driver - failed at dkms build
Status in bcmwl package in Ubuntu:
New
Status in linux-signed-hwe-5.8 package in Ubuntu:
New
Bug description:
Linux-5.8-#34
incapability with broadcom wifi driver - failed at dkms build
Logs:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build# cat make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-34-generic
(x86_64)
Friday 08 January 2021 02:46:07 PM IST
make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:288:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/b
[Kernel-packages] [Bug 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Tags added: originate-from-1908661 -- 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/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Bug description: [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+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 1909495] Re: Unable to start BIOS VMs since Linux 5.10
Hi, I'll try to recreate this early next week as time runs out today for me. But to prep for that when you say "stucks on pause" does that mean that e.g. "virsh list" shows them as paused? If that is the case, of one of the paused systems I'd expect some message in /var/log/libvirt/qemu/.log. Could you have a look and post one of those logs please? -- 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/1909495 Title: Unable to start BIOS VMs since Linux 5.10 Status in libvirt package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this all VMs on OVMF starts well. 5.10 took from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb
[Kernel-packages] [Bug 1910709] [NEW] DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Public bug reported: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; [...] Full DKMS log file attacked. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1910709/+attachment/5450642/+files/make.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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: New Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910709/+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 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1907559 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:17:15 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+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 1910709] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1910709 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: groovy -- 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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910709/+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 1905182] Re: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
I have this problem too. Kernel version: linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 Grafic card version: == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd11B6sv103Csd2255bc03sc00i00 vendor : NVIDIA Corporation model: GK104GLM [Quadro K3100M] Crash log in attach file ** Attachment added: "nvidia-dkms-390.0.crash" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1905182/+attachment/5450678/+files/nvidia-dkms-390.0.crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1905182 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Ran into this while installing linux-lowlatency-hwe-20.04-edge on a Dell Latitude E6520 with NVIDIA NVS 4200M graphics. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-29-lowlatency Date: Sun Nov 22 12:05:26 2020 DuplicateSignature: dkms:nvidia-dkms-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-01-05 (322 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2020-05-13 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1905182/+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 1905182] Re: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
On version 390.141 this bug has resolved -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1905182 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Ran into this while installing linux-lowlatency-hwe-20.04-edge on a Dell Latitude E6520 with NVIDIA NVS 4200M graphics. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-29-lowlatency Date: Sun Nov 22 12:05:26 2020 DuplicateSignature: dkms:nvidia-dkms-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-01-05 (322 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2020-05-13 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1905182/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
apport information ** Tags added: apport-collected focal ** Description changed: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-04 (64 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Gigabyte Technology Co., Ltd. H81M-D3H + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-59-generic N/A + linux-backports-modules-5.4.0-59-generic N/A + linux-firmware1.187.7 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-59-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 01/20/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F2 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H81M-D3H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: H81M-D3H + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450724/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte
[Kernel-packages] [Bug 1910709] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450727/+files/CRDA.txt ** Description changed: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-04 (64 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Gigabyte Technology Co., Ltd. H81M-D3H + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.4.0-59-generic N/A + linux-backports-modules-5.4.0-59-generic N/A + linux-firmware1.187.7 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-59-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 01/20/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F2 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H81M-D3H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: H81M-D3H + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. http
[Kernel-packages] [Bug 1910709] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450746/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.
[Kernel-packages] [Bug 1910709] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450739/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.produc
[Kernel-packages] [Bug 1910709] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450744/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by
[Kernel-packages] [Bug 1910709] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450738/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name:
[Kernel-packages] [Bug 1910709] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450735/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dm
[Kernel-packages] [Bug 1910709] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450733/+files/AudioDevicesInUse.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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O
[Kernel-packages] [Bug 1910709] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450742/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.
[Kernel-packages] [Bug 1910709] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450740/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name:
[Kernel-packages] [Bug 1910709] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450748/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.nam
[Kernel-packages] [Bug 1910709] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450741/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.
[Kernel-packages] [Bug 1910709] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450743/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.
[Kernel-packages] [Bug 1910709] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450732/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.produc
[Kernel-packages] [Bug 1910709] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450745/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M.
[Kernel-packages] [Bug 1910709] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450734/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H
[Kernel-packages] [Bug 1910709] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450736/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.produc
[Kernel-packages] [Bug 1910709] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450726/+files/AudioDevicesInUse.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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O
[Kernel-packages] [Bug 1910709] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450749/+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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.pr
[Kernel-packages] [Bug 1910709] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1910709/+attachment/5450750/+files/acpidump.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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.produc
[Kernel-packages] [Bug 1910738] [NEW] package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new
Public bug reported: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (748 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35.1 SourcePackage: linux Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (76 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package groovy -- 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/1910738 Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux- modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new'
[Kernel-packages] [Bug 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
ps: after the crash Nvidia doesn't recover yet, there is no "Kernel driver in use" [a@T520-i5:~$ lspci -nnk | egrep -i "VGA|3D|Display" -A2 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21d1] Kernel driver in use: i915 -- 00:16.3 Serial controller [0700]: Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) Subsystem: Lenovo 6 Series/C200 Series Chipset Family KT Controller [17aa:21cf] Kernel driver in use: serial -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d1] Kernel modules: nvidiafb, nouveau ] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1907559 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:17:15 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+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 1910738] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1910738 Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux- modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (748 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35.1 SourcePackage: linux Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (76 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910738/+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 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
I use Ubuntu 20.04 on a Thinkpad T520 and I changed from Nouveau to Invidia drivers after I had a lot of problems with libreoffice 6.4.6.2 and 7. I hpoe you can fix the problem. thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1907559 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:17:15 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+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 1910738] Re: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new':
** Tags removed: need-duplicate-check -- 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/1910738 Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux- modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (748 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35.1 SourcePackage: linux Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (76 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910738/+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 1910739] [NEW] package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error e
Public bug reported: The package could,'t be installed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 11:58:28 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-06-26 (195 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910739 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: The package could,'t be installed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 11:58:28 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-06-26 (195 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910739/+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 1910739] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910739 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: The package could,'t be installed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 11:58:28 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-06-26 (195 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910739/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
@daniel-banobre-dopico Can you confirm this affects the 'released' (focal-updates) kernel 5.8.0-36-generic (install linux-generic-hwe-20.04) ? -- 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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.
[Kernel-packages] [Bug 1910742] [NEW] Hirsute update: v5.10.5 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.10.5 upstream stable release
from git://git.kernel.org/
Linux 5.10.5
device-dax: Fix range release
ext4: avoid s_mb_prefetch to be zero in individual scenarios
dm verity: skip verity work if I/O error when system is shutting down
ALSA: pcm: Clear the full allocated memory at hw_params
io_uring: remove racy overflow list fast checks
s390: always clear kernel stack backchain before calling functions
tick/sched: Remove bogus boot "safety" check
drm/amd/display: updated wm table for Renoir
ceph: fix inode refcount leak when ceph_fill_inode on non-I_NEW inode fails
NFSv4.2: Don't error when exiting early on a READ_PLUS buffer overflow
um: ubd: Submit all data segments atomically
um: random: Register random as hwrng-core device
watchdog: rti-wdt: fix reference leak in rti_wdt_probe
fs/namespace.c: WARN if mnt_count has become negative
powerpc/64: irq replay remove decrementer overflow check
module: delay kobject uevent until after module init call
f2fs: fix race of pending_pages in decompression
f2fs: avoid race condition for shrinker count
NFSv4: Fix a pNFS layout related use-after-free race when freeing the inode
i3c master: fix missing destroy_workqueue() on error in i3c_master_register
powerpc: sysdev: add missing iounmap() on error in mpic_msgr_probe()
rtc: pl031: fix resource leak in pl031_probe
quota: Don't overflow quota file offsets
module: set MODULE_STATE_GOING state when a module fails to load
rtc: sun6i: Fix memleak in sun6i_rtc_clk_init
io_uring: check kthread stopped flag when sq thread is unparked
fcntl: Fix potential deadlock in send_sig{io, urg}()
ext4: check for invalid block size early when mounting a file system
bfs: don't use WARNING: string when it's just info.
ALSA: rawmidi: Access runtime->avail always in spinlock
ALSA: seq: Use bool for snd_seq_queue internal flags
f2fs: fix shift-out-of-bounds in sanity_check_raw_super()
media: gp8psk: initialize stats at power control logic
misc: vmw_vmci: fix kernel info-leak by initializing dbells in
vmci_ctx_get_chkpt_doorbells()
reiserfs: add check for an invalid ih_entry_count
fbcon: Disable accelerated scrolling
Bluetooth: hci_h5: close serdev device and free hu in h5_close
scsi: cxgb4i: Fix TLS dependency
zlib: move EXPORT_SYMBOL() and MODULE_LICENSE() out of dfltcc_syms.c
cgroup: Fix memory leak when parsing multiple source parameters
tools headers UAPI: Sync linux/const.h with the kernel headers
uapi: move constants from to
io_uring: fix io_sqe_files_unregister() hangs
io_uring: add a helper for setting a ref node
io_uring: use bottom half safe lock for fixed file data
io_uring: don't assume mm is constant across submits
lib/zlib: fix inflating zlib streams on s390
mm: memmap defer init doesn't work as expected
mm/hugetlb: fix deadlock in hugetlb_cow error path
scsi: block: Fix a race in the runtime power management code
opp: Call the missing clk_put() on error
opp: fix memory leak in _allocate_opp_table
spi: dw-bt1: Fix undefined devm_mux_control_get symbol
jffs2: Fix NULL pointer dereference in rp_size fs option parsing
jffs2: Allow setting rp_size to zero during remounting
io_uring: close a small race gap for files cancel
drm/amd/display: Add get_dig_frontend implementation for DCEx
md/raid10: initialize r10_bio->read_slot before use.
ethtool: fix string set id check
ethtool: fix error paths in ethnl_set_channels()
mptcp: fix security context on server socket
net/sched: sch_taprio: reset child qdiscs before freeing them
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: 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/1910742
Title:
Hirsute update: v5.10.5 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Hirsute:
Confirmed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directl
[Kernel-packages] [Bug 1767971] Re: No such man page: kernel_lockdown.7
It doesn't look like it. 20.10 is still on manpages 5.08. ** Also affects: manpages (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: manpages (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: manpages (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Hirsute) Importance: Medium Status: Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: manpages (Ubuntu Groovy) Status: New => 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/1767971 Title: No such man page: kernel_lockdown.7 Status in linux package in Ubuntu: Invalid Status in manpages package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in manpages source package in Focal: New Status in linux source package in Groovy: Invalid Status in manpages source package in Groovy: Confirmed Status in linux source package in Hirsute: Invalid Status in manpages source package in Hirsute: Fix Released Status in Fedora: Unknown Bug description: When booting in secure boot mode, the Bionic kernel emits the following message: [ 52.035055] Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 But there is no such man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767971/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Doing: sudo apt update sudo apt install linux-headers-generic-hwe-20.04 [...] Building module: cleaning build area... [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; make -k module KERNDIR=/lib/modu les/5.8.0-36-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modu les/5.8.0-36-generic/build LD=/usr/bin/ld.bfd; make -C uvm module KERNEL_UNAME=5 .8.0-36-generic KBUILD_EXTMOD=/var/lib/dkms/nvidia-340/340.108/build/uvm (bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. ...done. Configurando linux-headers-generic-hwe-20.04 (5.8.0.36.40~20.04.21) ... Yes, I confirm. -- 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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in linux package in Ubuntu: Incomplete Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014
[Kernel-packages] [Bug 1909705] Re: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend
Hello Kai-Heng, or anyone else affected, Accepted linux-firmware into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.190.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Confirmed => Fix Released ** Changed in: linux-firmware (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: linux-firmware (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+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 1909705] Please test proposed package
Hello Kai-Heng, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+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 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
Hello AceLan, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+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 1910749] [NEW] stop building nvidia dkms on kernels with no lrm
Public bug reported: [Impact] Building these modules wastes build time, and also may potentially lead to unnecessary updates. [Fix] Set do_dkms_nvidia = false on amd64.mk. [Test case] Build test the kernel. [Potential regression] Missing signed bits for these modules, in case users use them somewhat, without our support. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low -- 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/1910749 Title: stop building nvidia dkms on kernels with no lrm Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Building these modules wastes build time, and also may potentially lead to unnecessary updates. [Fix] Set do_dkms_nvidia = false on amd64.mk. [Test case] Build test the kernel. [Potential regression] Missing signed bits for these modules, in case users use them somewhat, without our support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910749/+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 1773598] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1773598 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 1 Status in bcmwl package in Ubuntu: Confirmed Bug description: wifi driver not installing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 27 00:32:25 2018 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-05-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source 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/bcmwl/+bug/1773598/+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 1910749] Re: stop building nvidia dkms on kernels with no lrm
** Description changed: [Impact] Building these modules wastes build time, and also may potentially lead to unnecessary updates. [Fix] Set do_dkms_nvidia = false on amd64.mk. [Test case] Build test the kernel. [Potential regression] - Missing signed bits for these modules, in case users use them somewhat, without our support. + Missing signed bits for these modules, in case someone uses them without LRMs. -- 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/1910749 Title: stop building nvidia dkms on kernels with no lrm Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Building these modules wastes build time, and also may potentially lead to unnecessary updates. [Fix] Set do_dkms_nvidia = false on amd64.mk. [Test case] Build test the kernel. [Potential regression] Missing signed bits for these modules, in case someone uses them without LRMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910749/+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 1910503] Re: latest kernel breaks display full sizing in virtualbox
6.1.16 is now in focal-proposed -- 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/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910503/+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 1852002] Re: Desktop frozen for 30 seconds after Nvidia driver crash
I think I have a very related (or the same) error (or multiple errors). A lot of logs here: https://askubuntu.com/questions/1236721/desktop-hung-up-freeze-gpuwatchdog-segfault-nvidia-frontend-close (Not sure if they are all the same cause, or different... I think they are the same.) When you search the Internet for "NVRM: Xid 31" errors, you will find quite a lot of results, also a lot of recent results. In my (most recent) case, I have Nvidia driver 450.80.02, and Linux kernel 5.4.0-59. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Hi, I just experienced a frozen desktop, where I could barely move the mouse, for maybe 30 seconds or more. When the desktop recovered, I looked at dmesg logs to find these lines: [ 461.937702] NVRM: GPU at PCI::01:00: GPU-734060ac-116d-fbbb-1553-d84896b846a4 [ 461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ It looks like a fault from the Nvidia driver. I'm using the tested one "nvidia-driver-435", installed via the GUI tool. Could you report this to Nvidia please ? Thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 17:35:12 2019 InstallationDate: Installed on 2019-09-26 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+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 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 solved it! Thanks armishra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 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.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+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 1909814] Re: Keyboard not working
When you close the lid keyboard backlight goes out. Then, as soon as you touch a key, it pops on. So the keyboard is responding... -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 it helped! Thanks... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 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.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+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 1910503] Re: latest kernel breaks display full sizing in virtualbox
** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Also affects: virtualbox (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) 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/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: New Status in linux source package in Focal: New Status in virtualbox source package in Focal: New Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910503/+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 1909495] Re: Unable to start BIOS VMs since Linux 5.10
** Attachment added: "VM log" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1909495/+attachment/5450917/+files/Kubuntu-20.04-x86_64-16GiB-MBR.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/1909495 Title: Unable to start BIOS VMs since Linux 5.10 Status in libvirt package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this all VMs on OVMF starts well. 5.10 took from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i
[Kernel-packages] [Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
You're welcome. -- 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/1909495 Title: Unable to start BIOS VMs since Linux 5.10 Status in libvirt package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Since 5.10 trying to start any VM with BIOS fails on start. There are stucks on pause immediately after start. Unlike this all VMs on OVMF starts well. 5.10 took from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/ $ LC_ALL=C virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (cli:204) Launched with command line: /usr/bin/virt-manager --debug [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:163) virt-manager version: 3.2.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:164) virtManager import: /usr/share/virt-manager/virtManager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:201) PyGObject version: 3.38.0 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (virtmanager:205) GTK version: 3.24.23 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:77) Using AppIndicator3 for systray [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (systray:463) Showing systray: False [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (inspection:206) python guestfs is not installed [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:113) Loading stored URIs: qemu+ssh://master@192.168.3.9/system qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:461) processing cli command uri= show_window=manager domain= [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:464) No cli action requested, launching default window [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (manager:185) Showing manager [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:316) window counter incremented to 1 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (engine:211) Initial gtkapplication activated [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:902) Scheduling background open thread for qemu:///system [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:952) libvirt version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:953) daemon version=6006000 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:954) conn version=500 [Mon, 28 Dec 2020 20:49:17 virt-manager 14579] DEBUG (connection:955) qemu:///system capabilities: a003001e-8c00-00b2-edcd-90e6ba5d1364 x86_64 Penryn Intel tcp rdma 14324000 3581000 0 apparmor 0 dac 0 +64055:+108 +64055:+108 hvm 32 /usr/bin/qemu-system-i386 pc-i440fx-groovy ubuntu pc-i440fx-2.12 pc-i440fx-2.0 pc-i440fx-xenial pc-q35-4.2 pc-i440fx-2.5 pc-i440fx-4.2 pc-i440fx-focal pc-q35-xenial pc-i440fx-1.5 pc-q35-2.7 pc-q35-eoan-hpb pc-i440fx-disco-hpb pc-i440fx-zesty pc-q35-groovy ubuntu-q35 pc-q35-artful pc-i440fx-trusty pc-i440fx-2.2 pc-i440fx-eoan-hpb pc-q35-focal-hpb pc-1.1 pc-q35-bionic-hpb pc-i440fx-artful pc-i440fx-2.7 pc-i440fx-yakkety pc-q35-2.4 pc-q35-cosmic-hpb pc-q35-2.10 pc-i440fx-1.7 pc-q35-2.9 pc-i440fx-2.11 pc-q35-3.1 pc-q35-4.1 pc-i440fx-2.4 pc-1.3 pc-i440fx-4.1 pc-q35-eoan pc-i440fx-2.9 pc-i440fx-bionic-hpb isapc pc-i440fx-1.4 pc-q35-cosmic pc-q35-2.6 pc-i440fx-3.1 pc-q35-bionic pc-q35-disco-hpb pc-i440fx-cosmic pc-q35-2.12 pc-i440fx-bionic pc-q35-groovy-hpb pc-q35-disco pc-i440fx-cosmic-hpb pc-i440fx-2.1 pc-1.0 pc-i440fx-wily pc-i440fx-2.6 pc-q35-4.0.1 pc-i440fx-1.6 pc-q35-5.0 q35 pc-q35-2.8 pc-i440fx
[Kernel-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed
I'm sorry, the apport-collect comment also results in a hanging process. See this bug: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 Thanks armishra! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 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.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+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 1910566] [NEW] Problem with the CH341 driver in Ubuntu 20.04
You have been subscribed to a public bug: I run into this problem trying to program an ESP8266 board, which uses the CH341 chip in the programming interface as a USB-to-Serial interface. The problem appeared after an upgrade from Ubuntu 19.10 to 20.04 (that I carried out one week ago). This is the kernel I am using: === $ uname -r 5.4.0-58-generic === When I connect the ESP8266 board (a Wemos D1 mini) to the USB there is no activity on the syslog (or dmesg), and the kernel module is not loaded. In fact I do not see the /dev/ttyACM0 device in the /dev directory and no useful device appears in the Arduino GUI. I have found the module in the kernel tree but, even forcing the installation, nothing happens: === augusto@Legion:~$ ls /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch* /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch341.ko augusto@Legion:~$ sudo modprobe ch341 [sudo] password di augusto: augusto@Legion:~$ lsusb Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 005: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 006: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub augusto@Legion:~$ lsmod | grep ch34 ch341 20480 0 usbserial 53248 1 ch341 === Without this module it is impossible to work with a relevant number of SBC devices, besides the named Wemos D1 Mini. Trying to solve the problem I also downloaded and installed the module source from https://github.com/juliagoda/CH341SER and compiled on my PC, after removing the "secure boot" feature. I recovered the module installation trace from the syslog files in the previous installation Ubuntu 19.10. The kernel version was probably 5.3.0-64-generic. As said above, at that time the module was operating properly: you notice that the module is loaded and later used to update a sketch: == Dec 30 12:22:43 Legion kernel: [2354065.515635] usb 1-3: new full-speed USB device number 30 using xhci_hcd Dec 30 12:22:43 Legion kernel: [2354065.664692] usb 1-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 Dec 30 12:22:43 Legion kernel: [2354065.664697] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Dec 30 12:22:43 Legion kernel: [2354065.664701] usb 1-3: Product: USB Serial Dec 30 12:22:43 Legion kernel: [2354065.666768] ch341 1-3:1.0: ch341-uart converter detected Dec 30 12:22:43 Legion kernel: [2354065.667695] usb 1-3: ch341-uart converter now attached to ttyUSB1 Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:43 Legion snapd[15280]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:45 Legion ModemManager[1198]: Couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/1-3': not supported by any plugin Dec 30 12:22:46 Legion systemd[6301]: tracker-extract.service: Succeeded. Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.52054' (uid=1000 pid=18287 comm="/usr/bin/gnome-shell " label="unconfined") Dec 30 12:22:46 Legion systemd[1]: Starting Fingerprint Authentication Daemon... Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 30 12:22:46 Legion systemd[1]: Started Fingerprint Authentication Daemon. Dec 30 12:22:50 Legion NetworkManager[1193]: [1609327370.5477] agent-manager: req[0x5574cc0e7540, :1.52054/org.gnome.Shell.NetworkAgent/1000]: agent registered Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.87/org/ayatana/NotificationItem/software_update_available Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/org/ayatana/NotificationItem/dropbox_client_18678 Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.110/org/ayatana/NotificationItem/whatsdesk1 Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-FATAL] unable to update overlay icon Dec 30 12:22:50 Legion gnome-shell[18287]: message repeated 5 times: [ [AppIndicatorSupport-FATAL] unable to update overlay icon] Dec 30 12:22:50 Legion gnome-shell[18287]: Couldn’t parse user-home.desktop as a desktop file, wil
[Kernel-packages] [Bug 1905591] Re: no brightness control after update from 450 to 455
@ddadap: No, nvidia-460 does not fix this regression. I've just tested
nvidia-driver-460 (460.32.03-0ubuntu0.18.04.1) and I observe that it
still misbehaves exactly as described above for 455: The initial
brightness is unusually dim and cannot be changed by any means. (Also,
just like 455, some pixel garbage appears during mode switch).
Reverting to 450 restores normal brightness functionality.
This regression makes nvidia-460 (and nvidia-455) unusable, and
manifests on multiple modern laptops.
@djve60: FYI, the (still defective) nvidia-460 packages are now available in
the archive, making testing 460 pretty painless at least:
To install 460:
sudo apt install nvidia-kernel-common-460 nvidia-driver-460
To revert to 450:
sudo apt install nvidia-kernel-common-450 nvidia-driver-450
@djve60, I recommend that you go ahead and test 460 that way to
determine whether your P76 sees any benefit or still fails like my X1
Extreme.
** Summary changed:
- no brightness control after update from 450 to 455
+ no brightness control in {455,460} after update from 450
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Triaged
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]
Updating to nvidia-driver-455 results in loss of brightness control.
On boot, the laptop display brightness is somewhat less than fully
bright and cannot be changed. The brightness up/down keys do pop up
the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/*
values do change, but the actual display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA). Normal functionality returns if I
downgrade to any version of nvidia-driver-450.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1910566] Re: Problem with the CH341 driver in Ubuntu 20.04
** Project changed: kernel => linux (Ubuntu) -- 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/1910566 Title: Problem with the CH341 driver in Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I run into this problem trying to program an ESP8266 board, which uses the CH341 chip in the programming interface as a USB-to-Serial interface. The problem appeared after an upgrade from Ubuntu 19.10 to 20.04 (that I carried out one week ago). This is the kernel I am using: === $ uname -r 5.4.0-58-generic === When I connect the ESP8266 board (a Wemos D1 mini) to the USB there is no activity on the syslog (or dmesg), and the kernel module is not loaded. In fact I do not see the /dev/ttyACM0 device in the /dev directory and no useful device appears in the Arduino GUI. I have found the module in the kernel tree but, even forcing the installation, nothing happens: === augusto@Legion:~$ ls /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch* /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch341.ko augusto@Legion:~$ sudo modprobe ch341 [sudo] password di augusto: augusto@Legion:~$ lsusb Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 005: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 006: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub augusto@Legion:~$ lsmod | grep ch34 ch341 20480 0 usbserial 53248 1 ch341 === Without this module it is impossible to work with a relevant number of SBC devices, besides the named Wemos D1 Mini. Trying to solve the problem I also downloaded and installed the module source from https://github.com/juliagoda/CH341SER and compiled on my PC, after removing the "secure boot" feature. I recovered the module installation trace from the syslog files in the previous installation Ubuntu 19.10. The kernel version was probably 5.3.0-64-generic. As said above, at that time the module was operating properly: you notice that the module is loaded and later used to update a sketch: == Dec 30 12:22:43 Legion kernel: [2354065.515635] usb 1-3: new full-speed USB device number 30 using xhci_hcd Dec 30 12:22:43 Legion kernel: [2354065.664692] usb 1-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 Dec 30 12:22:43 Legion kernel: [2354065.664697] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Dec 30 12:22:43 Legion kernel: [2354065.664701] usb 1-3: Product: USB Serial Dec 30 12:22:43 Legion kernel: [2354065.666768] ch341 1-3:1.0: ch341-uart converter detected Dec 30 12:22:43 Legion kernel: [2354065.667695] usb 1-3: ch341-uart converter now attached to ttyUSB1 Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:43 Legion snapd[15280]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:45 Legion ModemManager[1198]: Couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/1-3': not supported by any plugin Dec 30 12:22:46 Legion systemd[6301]: tracker-extract.service: Succeeded. Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.52054' (uid=1000 pid=18287 comm="/usr/bin/gnome-shell " label="unconfined") Dec 30 12:22:46 Legion systemd[1]: Starting Fingerprint Authentication Daemon... Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 30 12:22:46 Legion systemd[1]: Started Fingerprint Authentication Daemon. Dec 30 12:22:50 Legion NetworkManager[1193]: [1609327370.5477] agent-manager: req[0x5574cc0e7540, :1.52054/org.gnome.Shell.NetworkAgent/1000]: agent registered Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.87/org/ayatana/NotificationItem/software_update_available Dec 30 12:22:50 Legion gnome-shell[18287]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/org/ayatana/NotificationItem/dropbox_client_18678 Dec 30 12:22:50 Legion
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
** Description changed:
- On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX
- 1050 Ti Mobile]
- Updating to nvidia-driver-455 results in loss of brightness control. On
- boot, the laptop display brightness is somewhat less than fully bright
- and cannot be changed. The brightness up/down keys do pop up the gnome
- gui brightness widget, and /sys/class/backlight/nvidia_0/* values do
- change, but the actual display's brightness does not.
+ WORKS FINE:
+ nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
+
+ NO BRIGHTNESS CONTROL:
+ nvidia-driver-455: 455.38-0ubuntu0.18.04.1
+ nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
+
+
+ On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050
Ti Mobile], and other laptop model(s):
+
+ Updating to nvidia-driver-455 (or -460) results in loss of brightness
+ control. On boot, the laptop display brightness is somewhat less than
+ fully bright and cannot be changed. The brightness up/down keys do pop
+ up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/*
+ values do change, but the actual display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive or
- the ~graphics-drivers/PPA). Normal functionality returns if I downgrade
- to any version of nvidia-driver-450.
+ the ~graphics-drivers/PPA) or any version of -460.
+
+ Normal functionality returns if I downgrade to any version of nvidia-
+ driver-450.
+
+ Also observed: 455 and 460 temporarily display some pixel garbage while
+ mode-switching during the graphic login sequence. Only a minor glitch,
+ but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
-
- nvidia-driver-455: 455.38-0ubuntu0.18.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Triaged
Bug description:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050
Ti Mobile], and other laptop model(s):
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1910566] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1910566 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- 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/1910566 Title: Problem with the CH341 driver in Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I run into this problem trying to program an ESP8266 board, which uses the CH341 chip in the programming interface as a USB-to-Serial interface. The problem appeared after an upgrade from Ubuntu 19.10 to 20.04 (that I carried out one week ago). This is the kernel I am using: === $ uname -r 5.4.0-58-generic === When I connect the ESP8266 board (a Wemos D1 mini) to the USB there is no activity on the syslog (or dmesg), and the kernel module is not loaded. In fact I do not see the /dev/ttyACM0 device in the /dev directory and no useful device appears in the Arduino GUI. I have found the module in the kernel tree but, even forcing the installation, nothing happens: === augusto@Legion:~$ ls /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch* /usr/lib/modules/5.4.0-58-generic/kernel/drivers/usb/serial/ch341.ko augusto@Legion:~$ sudo modprobe ch341 [sudo] password di augusto: augusto@Legion:~$ lsusb Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 005: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 006: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub augusto@Legion:~$ lsmod | grep ch34 ch341 20480 0 usbserial 53248 1 ch341 === Without this module it is impossible to work with a relevant number of SBC devices, besides the named Wemos D1 Mini. Trying to solve the problem I also downloaded and installed the module source from https://github.com/juliagoda/CH341SER and compiled on my PC, after removing the "secure boot" feature. I recovered the module installation trace from the syslog files in the previous installation Ubuntu 19.10. The kernel version was probably 5.3.0-64-generic. As said above, at that time the module was operating properly: you notice that the module is loaded and later used to update a sketch: == Dec 30 12:22:43 Legion kernel: [2354065.515635] usb 1-3: new full-speed USB device number 30 using xhci_hcd Dec 30 12:22:43 Legion kernel: [2354065.664692] usb 1-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 Dec 30 12:22:43 Legion kernel: [2354065.664697] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Dec 30 12:22:43 Legion kernel: [2354065.664701] usb 1-3: Product: USB Serial Dec 30 12:22:43 Legion kernel: [2354065.666768] ch341 1-3:1.0: ch341-uart converter detected Dec 30 12:22:43 Legion kernel: [2354065.667695] usb 1-3: ch341-uart converter now attached to ttyUSB1 Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:43 Legion snapd[15280]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Dec 30 12:22:43 Legion mtp-probe: checking bus 1, device 30: "/sys/devices/pci:00/:00:14.0/usb1/1-3" Dec 30 12:22:43 Legion mtp-probe: bus: 1, device: 30 was not an MTP device Dec 30 12:22:45 Legion ModemManager[1198]: Couldn't check support for device '/sys/devices/pci:00/:00:14.0/usb1/1-3': not supported by any plugin Dec 30 12:22:46 Legion systemd[6301]: tracker-extract.service: Succeeded. Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.52054' (uid=1000 pid=18287 comm="/usr/bin/gnome-shell " label="unconfined") Dec 30 12:22:46 Legion systemd[1]: Starting Fingerprint Authentication Daemon... Dec 30 12:22:46 Legion dbus-daemon[1183]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 30 12:22:46
[Kernel-packages] [Bug 1910280] Re: can't adjust my screen_brightness
Did you try removing "acpi_backlight=vendor" from kernel parameters? -- 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/1910280 Title: can't adjust my screen_brightness Status in linux package in Ubuntu: Confirmed Bug description: Im using my machine since 20.12.20 and use it in dual boot with windows10 alongside. Hotkeys and adjusting brightness via GUI both broken, since formatting the machine on day 1. Before formatting, adjusting brightness was possible in windows10, but not in ubuntu or other linux distro, that I tried out. There is no bar in the top right corner under the bar for adjusting the sound output. Because "The description is too long. If you have lots of text to add, attach a file to the bug instead." the description is added as .txt- file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bella 2076 F pulseaudio /dev/snd/pcmC0D0p: bella 2076 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 13:58:37 2021 InstallationDate: Installed on 2020-12-25 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20VH001CGE ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=2850ca84-1b0f-4cdd-ac66-5b9c964159e6 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET29W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VH001CGE 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:bvrR1FET29W(1.03):bd10/08/2020:svnLENOVO:pn20VH001CGE:pvrThinkPadL13Gen2:rvnLENOVO:rn20VH001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L13 Gen 2 dmi.product.name: 20VH001CGE dmi.product.sku: LENOVO_MT_20VH_BU_Think_FM_ThinkPad L13 Gen 2 dmi.product.version: ThinkPad L13 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910280/+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 1786013] Re: Packaging resync
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure-edge (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1786013] Re: Packaging resync
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure-edge (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => In Progress -- 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: In Progress Bug description: I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
There is no other effect of disabling CONFIG_BASE_FULL save for changing CONFIG_BASE_SMALL. CONFIG_BASE_SMALL won't have much effect save for other memory savings that really would be able to reduce some runtime performance. As for boot time, changing this setting should not be expected to cause any significant changes. At focal, we have: arch/x86/include/asm/mpspec.h: changes MAX_MP_BUSSES only on 32-bit systems. drivers/tty/vt/vc_screen.c: change is not effective on memory reducing as of commit fcdba07ee390d include/linux/udp.h: include/linux/xarray.h: kernel/futex.c: kernel/user.c: These are all reducing the initial size of hash structures, causing more list traversals to happen when there are hash collisions. From here, there would be some negative effect on runtime execution, but memory allocation of these hashes should not introduce significant boot time regression as I mentioned. So, all in all, there is really no reason to keep CONFIG_BASE_SMALL=1 in any of the kernels we ship. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Groovy) 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux source package in Focal: New Status in linux-kvm source package in Focal: New Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: New Bug description: I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1910784] [NEW] Focal update: v5.4.83 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.83 upstream stable release from git://git.kernel.org/ pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output pinctrl: baytrail: Fix pin being driven low for a while on gpiod_get(..., GPIOD_OUT_HIGH) usb: gadget: f_fs: Use local copy of descriptors for userspace copy USB: serial: kl5kusb105: fix memleak on open USB: serial: ch341: add new Product ID for CH341A USB: serial: ch341: sort device-id entries USB: serial: option: add Fibocom NL668 variants USB: serial: option: add support for Thales Cinterion EXS82 USB: serial: option: fix Quectel BG96 matching tty: Fix ->pgrp locking in tiocspgrp() tty: Fix ->session locking ALSA: hda/realtek: Fix bass speaker DAC assignment on Asus Zephyrus G14 ALSA: hda/realtek: Add mute LED quirk to yet another HP x360 model ALSA: hda/realtek: Enable headset of ASUS UX482EG & B9400CEA with ALC294 ALSA: hda/realtek - Add new codec supported for ALC897 ALSA: hda/generic: Add option to enforce preferred_dacs pairs ftrace: Fix updating FTRACE_FL_TRAMP cifs: allow syscalls to be restarted in __smb_send_rqst() cifs: fix potential use-after-free in cifs_echo_request() i2c: imx: Don't generate STOP condition if arbitration has been lost thunderbolt: Fix use-after-free in remove_unplugged_switch() drm/i915/gt: Program mocs:63 for cache eviction on gen9 scsi: mpt3sas: Fix ioctl timeout dm writecache: fix the maximum number of arguments powerpc/64s/powernv: Fix memory corruption when saving SLB entries on MCE genirq/irqdomain: Add an irq_create_mapping_affinity() function powerpc/pseries: Pass MSI affinity to irq_create_mapping() dm: fix bug with RCU locking in dm_blk_report_zones dm: remove invalid sparse __acquires and __releases annotations x86/uprobes: Do not use prefixes.nbytes when looping over prefixes.bytes coredump: fix core_pattern parse error mm: list_lru: set shrinker map bit when child nr_items is not zero mm/swapfile: do not sleep with a spin lock held speakup: Reject setting the speakup line discipline outside of speakup i2c: imx: Fix reset of I2SR_IAL flag i2c: imx: Check for I2SR_IAL after every byte spi: bcm2835: Release the DMA channel if probe fails after dma_init iommu/amd: Set DTE[IntTabLen] to represent 512 IRTEs tracing: Fix userstacktrace option for instances lib/syscall: fix syscall registers retrieval on 32-bit platforms can: af_can: can_rx_unregister(): remove WARN() statement from list operation sanity check gfs2: check for empty rgrp tree in gfs2_ri_update netfilter: ipset: prevent uninit-value in hash_ip6_add tipc: fix a deadlock when flushing scheduled work ASoC: wm_adsp: fix error return code in wm_adsp_load() rtw88: debug: Fix uninitialized memory in debugfs code i2c: qup: Fix error return code in qup_i2c_bam_schedule_desc() dm writecache: remove BUG() and fail gracefully instead Input: i8042 - fix error return code in i8042_setup_aux() netfilter: nf_tables: avoid false-postive lockdep splat netfilter: nftables_offload: set address type in control dissector x86/insn-eval: Use new for_each_insn_prefix() macro to loop over prefixes bytes Linux 5.4.83 UBUNTU: upstream stable to v5.4.83 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either
[Kernel-packages] [Bug 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
** Description changed: + [Impact] + systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. + + [Fix] + Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. + + [Test case] + Write 419304 to /proc/sys/kernel/pid_max. + + [Potential regression] + Boot time may be affected. + + + + I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ - (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) + (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David -- 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux source package in Focal: New Status in linux-kvm source package in Focal: New Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: New Bug description: [Impact] systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. [Fix] Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. [Test case] Write 419304 to /proc/sys/kernel/pid_max. [Potential regression] Boot time may be affected. I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
Still the same issue with virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 on
kernel 5.8.0.36.40~20.04.21 from linux-image-generic-hwe-20.04-edge.
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in
[Kernel-packages] [Bug 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
** Changed in: linux-kvm (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu Groovy) Status: Fix Committed => In Progress ** Changed in: linux-kvm (Ubuntu) Importance: High => Medium ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux-kvm (Ubuntu) Assignee: Thadeu Lima de Souza Cascardo (cascardo) => (unassigned) -- 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: In Progress Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: In Progress Status in linux source package in Focal: New Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: In Progress Bug description: [Impact] systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. [Fix] Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. [Test case] Write 419304 to /proc/sys/kernel/pid_max. [Potential regression] Boot time may be affected. I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1905591] Re: no brightness control in {455, 460} after update from 450
The 460 driver package was installed with the latest updates and I've
rebooted.
For me, at least, it's working perfectly again.
And I made a mistake on my machine type: it's a ThinkPad P73.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Triaged
Bug description:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050
Ti Mobile], and other laptop model(s):
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I think the problem was in the headphones. I found I was having trouble on my phone as well. I contacted Sony support and they had me try a soft reset of the headset, which seems to have restored function. I am still getting bad mic sound on bluetooth, but I think it is just the low quality sound on this thread and not the completely muffled sound I was getting before. I will try reconnecting to the DG80 now and see if it is any better. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1910796] [NEW] package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
Public bug reported: No adapter wifi found my wifi faded away suddenly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elysium1878 F pulseaudio /dev/snd/controlC0: elysium1878 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 21:05:35 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-59.65 Unpacking linux-libc-dev:amd64 (5.4.0-60.67) over (5.4.0-59.65) ... dpkg: error processing archive /tmp/apt-dpkg-install-nkvRs4/10-linux-libc-dev_5.4.0-60.67_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-07-19 (173 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: LENOVO 20238 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4df4b488-8b85-439c-ac68-a02733c47c50 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN50WW(V3.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-package focal -- 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/1910796 Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: No adapter wifi found my wifi faded away suddenly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elysium1878 F pulseaudio /dev/snd/controlC0: elysium1878 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 21:05:35 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-59.65 Unpacking linux-libc-dev:amd64 (5.4.0-60.67) over (5.4.0-59.65) ... dpkg: error processing archive /tmp/apt-dpkg-install-nkvRs4/10-linux-libc-dev_5.4.0-60.67_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-07-19 (173 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: LENOVO 20238 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4df4b488-8b85-439c-ac68-a02733c47c50 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVe
[Kernel-packages] [Bug 1910796] Re: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
** Tags removed: need-duplicate-check -- 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/1910796 Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: No adapter wifi found my wifi faded away suddenly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elysium1878 F pulseaudio /dev/snd/controlC0: elysium1878 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 21:05:35 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-59.65 Unpacking linux-libc-dev:amd64 (5.4.0-60.67) over (5.4.0-59.65) ... dpkg: error processing archive /tmp/apt-dpkg-install-nkvRs4/10-linux-libc-dev_5.4.0-60.67_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-07-19 (173 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: LENOVO 20238 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4df4b488-8b85-439c-ac68-a02733c47c50 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN50WW(V3.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910796/+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 1910796] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1910796 Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: No adapter wifi found my wifi faded away suddenly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elysium1878 F pulseaudio /dev/snd/controlC0: elysium1878 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 21:05:35 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-59.65 Unpacking linux-libc-dev:amd64 (5.4.0-60.67) over (5.4.0-59.65) ... dpkg: error processing archive /tmp/apt-dpkg-install-nkvRs4/10-linux-libc-dev_5.4.0-60.67_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-07-19 (173 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: LENOVO 20238 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4df4b488-8b85-439c-ac68-a02733c47c50 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN50WW(V3.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910796/+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 1910496] Re: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1910496 Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: 123 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 09:20:34 2021 DuplicateSignature: dkms:nvidia-dkms-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-linux.h:512:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1910496/+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 1910796] Re: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
This is probably a 'feature' of your Sophos AV software. talpa_* modules are part of it: https://support.sophos.com/support/s/article/KB-37103 See also the various 'talpa' error messages in your kernel log: https://launchpadlibrarian.net/516159223/CurrentDmesg.txt ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910796 Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: No adapter wifi found my wifi faded away suddenly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elysium1878 F pulseaudio /dev/snd/controlC0: elysium1878 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 21:05:35 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-59.65 Unpacking linux-libc-dev:amd64 (5.4.0-60.67) over (5.4.0-59.65) ... dpkg: error processing archive /tmp/apt-dpkg-install-nkvRs4/10-linux-libc-dev_5.4.0-60.67_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-07-19 (173 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: LENOVO 20238 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4df4b488-8b85-439c-ac68-a02733c47c50 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-libc-dev 5.4.0-59.65 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN50WW(V3.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910796/+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 1905591] Re: no brightness control in {455, 460} after update from 450
** Description changed: + On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX + 1050 Ti Mobile]: WORKS FINE: nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1 NO BRIGHTNESS CONTROL: nvidia-driver-455: 455.38-0ubuntu0.18.04.1 nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1 - - On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile], and other laptop model(s): + *Note that 460 fixes it for Lenovo P73 per comment #6, but not for + Lenovo X1 per comment #5. Updating to nvidia-driver-455 (or -460) results in loss of brightness control. On boot, the laptop display brightness is somewhat less than fully bright and cannot be changed. The brightness up/down keys do pop up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/* values do change, but the actual display's brightness does not. Problem occurs with either version of nvidia-driver-455 (the archive or the ~graphics-drivers/PPA) or any version of -460. Normal functionality returns if I downgrade to any version of nvidia- driver-450. Also observed: 455 and 460 temporarily display some pixel garbage while mode-switching during the graphic login sequence. Only a minor glitch, but note that 450 does not exhibit that issue either. Note also that manually applying this to /lib/systemd/system/nvidia-persistenced.service has no effect on the problem: https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5 Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Description changed: On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile]: WORKS FINE: nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1 NO BRIGHTNESS CONTROL: nvidia-driver-455: 455.38-0ubuntu0.18.04.1 nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1 - *Note that 460 fixes it for Lenovo P73 per comment #6, but not for - Lenovo X1 per comment #5. + *Note that 460 fixes it for a 20.04 Lenovo P73 per comment #6, but not + for my 18.04.5 Lenovo X1 per comment #5. Updating to nvidia-driver-455 (or -460) results in loss of brightness control. On boot, the laptop display brightness is somewhat less than fully bright and cannot be changed. The brightness up/down keys do pop up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/* values do change, but the actual display's brightness does not. Problem occurs with either version of nvidia-driver-455 (the archive or the ~graphics-drivers/PPA) or any version of -460. Normal functionality returns if I downgrade to any version of nvidia- driver-450. Also observed: 455 and 460 temporarily display some pixel garbage while mode-switching during the graphic login sequence. Only a minor glitch, but note that 450 does not exhibit that issue either. Note also that manually applying this to /lib/systemd/system/nvidia-persistenced.service has no effect on the problem: https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5 Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Description changed: On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile]: WORKS FINE: nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1 NO BRIGHTNESS CONTROL: nvidia-driver-455: 455.38-0ubuntu0.18.04.1 nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1 - *Note that 460 fixes it for a 20.04 Lenovo P73 per comment #6, but not - for my 18.04.5 Lenovo X1 per comment #5. + *Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but not + for my 18.04.5 Lenovo ThinkPad X1 per comment #5. Updating to nvidia-driver-455 (or -460) results in loss of brightness control. On boot, the laptop display brightness is somewhat less than fully bright and cannot be changed. The brightness up/down keys do pop up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/* values do change, but the actual display's brightness does not. Problem occurs with either version of nvidia-driver-455 (the archive or the ~graphics-drivers/PPA) or any version of -460. Normal functionality returns if I downgrade to any version of nvidia- driver-450. Also observed: 455 and 460 temporarily display some pixel garbage while mode-switching during the graphic login sequence. Only a minor glitch, but note that 450 does not exhibit that issue either. Note also that manually applying this to /lib/systemd/system/nvidia-persistenced.service has no effect on the p
[Kernel-packages] [Bug 1904724] Re: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-
Possible duplicate report: bug 1910738 This is most likely a support topic, not a bug - please provide further information if you are convinced it is a bug. Support options (incl. free community support - on the bottom) are listed on https://ubuntu.com/support ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904724 Title: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: New kernel installation 5.8.0-29 was corrupted. Problem with sudo apt upgrade: You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies. linux-image-generic : Depends: linux-modules-extra-5.8.0-29-generic but it is not installed ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-extra-5.8.0-29-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1581 F pulseaudio CasperMD5CheckResult: skip Date: Wed Nov 18 11:50:28 2020 ErrorMessage: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (697 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35 SourcePackage: linux Title: package linux-modules-extra-5.8.0-29-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.8.0-29-generic/kernel/kernel/torture.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904724/+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 1910738] Re: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new':
Possible duplicate report: bug 1904724 Thanks for reporting. This is more likely a support topic, not a bug - please provide further information if you are convinced it is a bug. Support options (incl. free community support - on the bottom) are listed on https://ubuntu.com/support ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910738 Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux- modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: No problematic behaviour except for push-up notification showing this bug. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-36-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euler 1632 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 10:26:39 2021 DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb ... Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-36-generic:(not installed) Unpacking linux-modules-5.8.0-36-generic (5.8.0-36.40) ... dpkg: error processing archive /tmp/apt-dpkg-install-fkWCCt/0-linux-modules-5.8.0-36-generic_5.8.0-36.40_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-22 (748 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PC Specialist LTD N2x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: grub-pc 2.04-1ubuntu35.1 SourcePackage: linux Title: package linux-modules-5.8.0-36-generic (not installed) failed to install/upgrade: unable to open '/usr/share/doc/linux-modules-5.8.0-36-generic/copyright.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to groovy on 2020-10-23 (76 days ago) dmi.bios.date: 06/02/2018 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N2x0WU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.13:bd06/02/2018:br7.13:efr7.13:svnPCSpecialistLTD:pnN2x0WU:pvrNotApplicable:rvnCLEVO:rnN2x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N2x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910738/+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 1910806] [NEW] System hang - kernel 5.8.0-36
Public bug reported: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 errors: No known data errors jcw0624@cascade:~/Documents/Computing/Windows$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-36-generic 5.8.0-36.40 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245470 F pulseaudio /dev/snd/controlC1: jcw06245470 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 11:56:46 2021 InstallationDate: Installed on 2020-10-03 (97 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (60 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1910806 Title: System hang - kernel 5.8.0-36 Status in linux package in Ubuntu: New Bug description: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
In my case, closing the lid switch the screen off and it comes back as soon as I open the lid again. I will do other checks to see if keyboard if "alive". -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1910806] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1910806 Title: System hang - kernel 5.8.0-36 Status in linux package in Ubuntu: Confirmed Bug description: I reported what I believe to be the same problem yesterday with kernel -34 but running the rsync command to create a backup. I can cause the system to hang with the following commands: dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k cp Win10_20H2_v2_English_x64.iso /var/tmp The source file resides on a zfs filesystem in a raidz1 pool (4 x 4TB Seagate drives) These commands and the rsync work with kernel 5.8.0-33 The filename describes the contents. zpool scrub runs without errors... cw0624@cascade:~/Documents/Computing/Windows$ ls -l *.iso -rw-r--r-- 1 jcw0624 staff 6221846528 Dec 20 12:18 Win10_20H2_v2_English_x64.iso jcw0624@cascade:~/Documents/Computing/Windows$ zpool status pool: data state: ONLINE scan: scrub repaired 0B in 0 days 00:22:28 with 0 errors on Fri Jan 8 11:48:13 2021 config: NAMESTATE READ WRITE CKSUM dataONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 errors: No known data errors jcw0624@cascade:~/Documents/Computing/Windows$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-36-generic 5.8.0-36.40 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245470 F pulseaudio /dev/snd/controlC1: jcw06245470 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jan 8 11:56:46 2021 InstallationDate: Installed on 2020-10-03 (97 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (60 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910806/+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 1896119] Re: Catting the SecureBoot efivar in /sys hangs
** Changed in: plainbox-provider-checkbox Status: In Progress => Fix Committed -- 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/1896119 Title: Catting the SecureBoot efivar in /sys hangs Status in Provider for Plainbox - Checkbox: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: During testing, a machine locked up appearing to hang on the secure boot mode test. Looking at the test logs, both of the things that use boot_mode_test.py have triggered this issue: miscellanea/reboot_firmware crashed miscellanea/secure_boot_mode crashed as this doesn't do much beyond open up a file in efivars, this is puzzling behaviour. Need to figure out what would trigger this and how to work around it. To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1896119/+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 1909705] Re: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend
** Tags added: verification-done-focal verification-done-groovy -- 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/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Connected BLE devices like keyboard and mouse won't automatically reconnect to host after system suspend. [Fix] New firmware from Realtek. [Test] With the new firmware used, BLE keyboard and mouse will reconnect to host by pressing any key or by moving it. [Where problems could occur] Tried some other Bluetooth peripherals and didn't see any regression. This is also internally tested by Realtek. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+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 1866149] Re: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => Invalid -- 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/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Incomplete Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-kvm source package in Groovy: In Progress Bug description: [Impact] systemd-systemctl will fail to set kernel.pid_max, leading to a degraded boot. [Fix] Set CONFIG_BASE_FULL=y, CONFIG_BASE_SMALL=0. [Test case] Write 419304 to /proc/sys/kernel/pid_max. [Potential regression] Boot time may be affected. I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866149/+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 1910813] [NEW] Error when install libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb
Public bug reported: Preparing to unpack ... / libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb ... Unpacking libnvidia-compute-390: amd64 (390.141-0ubuntu0.20.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb (--unpack): trying to overwrite the generic "/etc/OpenCL/vendors/nvidia.icd" which is different from other instances of the libnvidia-compute-390: amd64 package dpkg-deb: error: insert subprocess was interrupted by signal (Broken pipe) Errors occurred while processing the following packets: /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb E: subprocess / usr / bin / dpkg returned error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 23:10:43 2021 InstallationDate: Installed on 2020-11-01 (68 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910813 Title: Error when install libnvidia-compute- 390_390.141-0ubuntu0.20.10.1_amd64.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Preparing to unpack ... / libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb ... Unpacking libnvidia-compute-390: amd64 (390.141-0ubuntu0.20.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb (--unpack): trying to overwrite the generic "/etc/OpenCL/vendors/nvidia.icd" which is different from other instances of the libnvidia-compute-390: amd64 package dpkg-deb: error: insert subprocess was interrupted by signal (Broken pipe) Errors occurred while processing the following packets: /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb E: subprocess / usr / bin / dpkg returned error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 23:10:43 2021 InstallationDate: Installed on 2020-11-01 (68 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910813/+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 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
Also affecting me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+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 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
Thank U very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1907559 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:17:15 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 390.138-0ubuntu0.20.04.1 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.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1910816] [NEW] Focal update: v5.4.84 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.84 upstream stable release from git://git.kernel.org/ Kbuild: do not emit debug info for assembly with LLVM_IAS=1 x86/lib: Change .weak to SYM_FUNC_START_WEAK for arch/x86/lib/mem*_64.S iwlwifi: pcie: limit memory read spin time arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards. iwlwifi: pcie: set LTR to avoid completion timeout iwlwifi: mvm: fix kernel panic in case of assert during CSA powerpc: Drop -me200 addition to build flags arm64: dts: broadcom: clear the warnings caused by empty dma-ranges ARC: stack unwinding: don't assume non-current task is sleeping scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE interconnect: qcom: qcs404: Remove GPU and display RPM IDs ibmvnic: skip tx timeout reset while in resetting irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts soc: fsl: dpio: Get the cpumask through cpumask_of(cpu) arm64: tegra: Disable the ACONNECT for Jetson TX2 platform/x86: thinkpad_acpi: Do not report SW_TABLET_MODE on Yoga 11e platform/x86: thinkpad_acpi: Add BAT1 is primary battery quirk for Thinkpad Yoga 11e 4th gen platform/x86: acer-wmi: add automatic keyboard background light toggle key as KEY_LIGHTS_TOGGLE platform/x86: intel-vbtn: Support for tablet mode on HP Pavilion 13 x360 PC platform/x86: touchscreen_dmi: Add info for the Irbis TW118 tablet can: m_can: m_can_dev_setup(): add support for bosch mcan version 3.3.0 ktest.pl: Fix incorrect reboot for grub2bls Input: cm109 - do not stomp on control URB Input: i8042 - add Acer laptops to the i8042 reset list pinctrl: amd: remove debounce filter setting in IRQ type setting mmc: block: Fixup condition for CMD13 polling for RPMB requests drm/i915/display/dp: Compute the correct slice count for VDSC on DP kbuild: avoid static_assert for genksyms proc: use untagged_addr() for pagemap_read addresses scsi: be2iscsi: Revert "Fix a theoretical leak in beiscsi_create_eqs()" x86/mm/mem_encrypt: Fix definition of PMD_FLAGS_DEC_WP x86/membarrier: Get rid of a dubious optimization x86/apic/vector: Fix ordering in vector assignment mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING UBUNTU: [Config] updateconfigs for PGTABLE_MAPPING compiler.h: fix barrier_data() on clang Linux 5.4.84 UBUNTU: upstream stable to v5.4.84 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.84 upstream stable release + from git://git.kernel.org/ -v5.4.84 upstream stable release -from git://git.kernel.org/ + Kbuild: do not emit debug info for assembly with LLVM_IAS=1 + x86/lib: Change .weak to SYM_FUNC_START_WEAK for arch/x86/lib/mem*_64.S + iwlwifi: pcie: limit memory read spin time + arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards. + iwlwifi: pcie: set LTR to avoid completion timeout + iwlwifi: mvm: fix kernel panic in case of assert during CSA + powerpc: Drop -me200 addition to build flags + arm64: dts: broadcom: clear the warnings caused by empty dma-ranges + ARC: stack unwinding: don't assume non-current task is sleeping + scsi: ufs: Make sure clk scaling happens only when HBA is
[Kernel-packages] [Bug 1902409] Re: bcmwl-kernel-source not supported on kernel package linux-headers-5.8.0-7625-generic
Having same issues with wifi after update of Ubuntu 20.04 pushed kernel 5.8. Had to go back to 5.4 kernel to have wifi recognized. Additionally, live usb 20.10 has same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1902409 Title: bcmwl-kernel-source not supported on kernel package linux- headers-5.8.0-7625-generic Status in bcmwl package in Ubuntu: Confirmed Bug description: I'm currently at 20.04 LTS with 5.8 kernel, the driver doesn't work and my wifi is dissappear. I've tried to reinstall the driver but it doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1902409/+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 1910817] [NEW] Focal update: v5.4.85 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.85 upstream stable release from git://git.kernel.org/ ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info() ipv4: fix error return code in rtm_to_fib_config() mac80211: mesh: fix mesh_pathtbl_init() error path net: bridge: vlan: fix error return code in __vlan_add() vrf: packets with lladdr src needs dst at input with orig_iif when needs strict net: hns3: remove a misused pragma packed udp: fix the proto value passed to ip_protocol_deliver_rcu for the segments enetc: Fix reporting of h/w packet counters bridge: Fix a deadlock when enabling multicast snooping net: stmmac: free tx skb buffer in stmmac_resume() tcp: select sane initial rcvq_space.space for big MSS tcp: fix cwnd-limited bug for TSO deferral where we send nothing net/mlx4_en: Avoid scheduling restart task if it is already running lan743x: fix for potential NULL pointer dereference with bare card net/mlx4_en: Handle TX error CQE net: ll_temac: Fix potential NULL dereference in temac_probe() net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux net: stmmac: delete the eee_ctrl_timer after napi disabled ktest.pl: If size of log is too big to email, email error message USB: dummy-hcd: Fix uninitialized array use in init() USB: add RESET_RESUME quirk for Snapscan 1212 ALSA: usb-audio: Fix potential out-of-bounds shift ALSA: usb-audio: Fix control 'access overflow' errors from chmap xhci: Give USB2 ports time to enter U3 in bus suspend xhci-pci: Allow host runtime PM as default for Intel Alpine Ridge LP USB: UAS: introduce a quirk to set no_write_same USB: sisusbvga: Make console support depend on BROKEN UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON ALSA: pcm: oss: Fix potential out-of-bounds shift serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access KVM: mmu: Fix SPTE encoding of MMIO generation upper half membarrier: Explicitly sync remote cores when SYNC_CORE is requested x86/resctrl: Remove unused struct mbm_state::chunks_bw x86/resctrl: Fix incorrect local bandwidth when mba_sc is enabled Linux 5.4.85 UBUNTU: upstream stable to v5.4.85 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.85 upstream stable release + from git://git.kernel.org/ -v5.4.85 upstream stable release -from git://git.kernel.org/ + ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info() + ipv4: fix error return code in rtm_to_fib_config() + mac80211: mesh: fix mesh_pathtbl_init() error path + net: bridge: vlan: fix error return code in __vlan_add() + vrf: packets with lladdr src needs dst at input with orig_iif when needs strict + net: hns3: remove a misused pragma packed + udp: fix the proto value passed to ip_protocol_deliver_rcu for the segments + enetc: Fix reporting of h/w packet counters + bridge: Fix a deadlock when enabling multicast snooping + net: stmmac: free tx skb buffer in stmmac_resume() + tcp: select sane initial rcvq_space.space for big MSS + tcp: fix cwnd-limited bug for TSO deferral where we send nothing +
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
this honestly looks like a simple case of warnings now being treated as errors. I can't imagine this is a sane thing to do for 3rd party code. Any fix soon? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+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 1910813] Re: Error when install libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb
If I delete file /etc/OpenCL/vendors/nvidia.icd then: Configuring the nvidia-compute-utils-390 (390.141-0ubuntu0.20.10.1) package ... Note: there is no access to the specified home directory / nonexistent: No such file or directory The system user "nvidia-persistenced" (UID 126) is added ... A new group "nvidia-persistenced" (GID 135) is added ... A new user "nvidia-persistenced" (UID 126) is added to the "nvidia-persistenced" group ... The home directory "/ nonexistent" is not created. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910813 Title: Error when install libnvidia-compute- 390_390.141-0ubuntu0.20.10.1_amd64.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Preparing to unpack ... / libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb ... Unpacking libnvidia-compute-390: amd64 (390.141-0ubuntu0.20.10.1) ... dpkg: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb (--unpack): trying to overwrite the generic "/etc/OpenCL/vendors/nvidia.icd" which is different from other instances of the libnvidia-compute-390: amd64 package dpkg-deb: error: insert subprocess was interrupted by signal (Broken pipe) Errors occurred while processing the following packets: /var/cache/apt/archives/libnvidia-compute-390_390.141-0ubuntu0.20.10.1_amd64.deb E: subprocess / usr / bin / dpkg returned error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 23:10:43 2021 InstallationDate: Installed on 2020-11-01 (68 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910813/+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 1909790] Re: wireless mouse middle click missing on new 20.04
Are you using Wayland or X11? (https://askubuntu.com/questions/904940 /how-can-i-tell-if-i-am-running-wayland) Try to switch to the other -- 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/1909790 Title: wireless mouse middle click missing on new 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Long time Ubuntu user. Fresh install of 20.04 on an older NUC. Everything works fine except the Logitech wireless mouse - M185 came in keyboard/mouse package. Actually the mouse works fine except there is no middle click. Middle wheel scrolls fine. LSUSB recognizes the receiver: Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver xinput test only recognizes button 1 and 3 $ xinput test 12 button press 1 button release 1 button press 3 button release 3 I installed Solaar but that didn't help, although I did like the Solaar battery gauge. The Ubuntu Mouse & Touchpad Settings doesn't show a middle button either. I miss my middle click paste. :-( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcw 1410 F pulseaudio /dev/snd/controlC0: marcw 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 31 20:10:46 2020 InstallationDate: Installed on 2020-12-28 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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.4.0-58-generic root=UUID=569d8094-8fe3-4d4e-b814-99989559626a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0072.2019.1001.1636 dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-506 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0072.2019.1001.1636:bd10/01/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-506:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909790/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Groovy) 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/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:b
[Kernel-packages] [Bug 1909687] Re: Cannot compile kernel using procedure at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
"apt-get source linux-image-unsigned-$(uname -r)" is updated to wiki page -- 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/1909687 Title: Cannot compile kernel using procedure at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the procedure to compile the kernel for ubuntu- bionic: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Here is the procedure that I tried to do: First, uncomment all deb-src in /etc/apt/sources.list apt-get update apt-get upgrade apt-get dist-upgrade Reboot machine Confirm version: maallyn@li1183-111:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic maallyn@li1183-111:~$ uname -a Linux li1183-111 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux sudo apt-get build-dep linux linux-image-$(uname -r) apt-get install libncurses-dev flex bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf apt-get source linux-image-$(uname -r) Is broken. I am getting permission denied even though I am on as root. root@li1183-111:~# apt-get source linux-image-$(uname -r) Reading package lists... Done Picking 'linux-signed' as source package instead of 'linux-image-4.15.0-128-generic' Need to get 19.8 kB of source archives. Get:1 http://mirrors.linode.com/ubuntu bionic-updates/main linux-signed 4.15.0-128.131 (dsc) [2,103 B] Get:2 http://mirrors.linode.com/ubuntu bionic-updates/main linux-signed 4.15.0-128.131 (tar) [17.7 kB] Fetched 19.8 kB in 0s (1,805 kB/s) dpkg-source: info: extracting linux-signed in linux-signed-4.15.0 dpkg-source: info: unpacking linux-signed_4.15.0-128.131.tar.xz W: Download is performed unsandboxed as root as file 'linux-signed_4.15.0-128.131.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ## # Now trying git clone method git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git This seems to work okay . . . maallyn@li1183-111:~$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git Cloning into 'ubuntu-bionic'... remote: Counting objects: 7717929, done. remote: Compressing objects: 100% (1127512/1127512), done. Receiving objects: 100% (7717929/7717929), 1.70 GiB | 18.82 MiB/s, done. remote: Total 7717929 (delta 6543888), reused 7715758 (delta 6541783) Resolving deltas: 100% (6543888/6543888), done. Checking out files: 100% (63373/63373), done. Now, trying to do the fakeroot, come to find that the procedure did not include apt-get install fakeroot Now the prep to do the configures seem to be okay Now, added allyn1 to version by changing the first line of debian.master/changelog: linux (4.15.0-126.129-allyn1) bionic; urgency=medium Change config to remove Nouveau (NVIDIA) cards from configuration so that I can use the propriatary NVIDIA drivers Changed only amd64 and amd64 lowlatency, but did not change others --- LANG=C fakeroot debian/rules binary-headers binary-generic binary-perarch I have made the entire output of the console available at: www.allyn.com/build-attempt.txt I have also made the entire (uncompiled) source tree available at: www.allyn.com/ubuntu-bionic.tar I can be contacted at markallyn...@gmail.com and my account at ubuntu is maallyn123 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-128-generic 4.15.0-128.131 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 30 17:06 seq crw-rw 1 root audio 116, 33 Dec 30 17:06 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Dec 30 18:54:36 2020 InstallationDate: Installed on 2020-09-28 (92 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PciMultimedia: ProcFB: 0 bochsdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 RelatedPackageVersions: li
