[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
That's odd. Those logs suggest the nvidia kernel driver built and installed successfully. But your log from bug 2025585 explains the issue: Jul 03 11:40:12 khteh-p17-2i gdm3[3370]: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service Jul 03 11:40:12 khteh-p17-2i kernel: Loading of module with unavailable key is rejected which is also mentioned in bug 1921536. -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
It looks like the nvidia kernel has been reverted. However, I am still seeing the same error with Slack, and the second monitor is still not working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2023946] Re: Nvidia 530 kernel driver is not installed/built
/var/log/apt/history.log /var/log/dpkg.log ** Attachment added: "nvidia.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2023946/+attachment/5683480/+files/nvidia.log -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry transforms ii
[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
/var/lib/dkms/nvidia/535.54.03/6.2.0-24-generic/x86_64/log/make.log ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2023946/+attachment/5683479/+files/make.log -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry
[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
That's unfortunate, but useful for debugging this. Please try to find the relevant log file from when it tried to build the kernel graphics driver: find /var/lib/dkms/nvidia -name \*.log Please also attach the system update logs: /var/log/apt/history.log /var/log/dpkg.log -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64
[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry transforms ii libnppim11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA
[Kernel-packages] [Bug 2025585] Re: Nvidia 530 kernel driver monitor resolution problem
Thanks for the bug report. It sounds like the HDMI connection isn't getting the full display info (sometimes). Next time it happens, please run: journalctl -b0 > journal.txt and attach the resulting text file here. It might be helpful to do the same also when the bug is NOT happening. ** Package changed: ubuntu => nvidia-graphics-drivers-530 (Ubuntu) ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: New => Incomplete ** Tags added: lunar multimonitor nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2025585 Title: Nvidia 530 kernel driver monitor resolution problem Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Bug description: I have managed to install the drivers and nvidia-smi shows output but it does NOT detect my external monitor which used to work with previous version of the driver. Sometimes it is detected by the resolution too small https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-530/+bug/2023946 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2025585/+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 2023946] Re: Nvidia 530 kernel driver is not installed/built
Was away for a week and today things break again after `apt update && apt upgrade` ! $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd6411.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd6411.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd6411.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd6411.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry transforms ii libnppim11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Morphological operations ii libnppist11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Statistics ii libnppisu11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Support ii libnppitc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Threshold and Compare ii libnpps11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives for signal processing runtime library ii libnvidia-cfg1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-535 535.54.03-0ubuntu0.23.04.2 all Shared files used by the NVIDIA libraries ii libnvidia-compute-535:amd64535.54.03-0ubuntu0.23.04.2 amd64NVIDIA libcompute package ii libnvidia-decode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-encode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVENC Video Encoding runtime library ii libnvidia-extra-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64Extra libraries for the NVIDIA driver ii libnvidia-fbc1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL-based Framebuffer Capture
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
Verified on both Pink Sardine and RPL DMIC devices for jammy and lunar, the mic-mute LED works correctly now. ** Tags removed: verification-needed verification-needed-jammy verification-needed-lunar ** Tags added: verification-done verification-done-jammy verification-done-lunar ** Changed in: oem-priority Status: New => Fix Released ** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2023946] Re: Nvidia 530 kernel driver is not installed/built
https://bugs.launchpad.net/ubuntu/+bug/2025585 -- 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/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in dkms package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Geometry transforms ii libnppim11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Morphological operations ii libnppist11:amd64
[Kernel-packages] [Bug 2025120] Re: Crash in ucsi_acpi_async_write [ucsi_acpi] prevents booting
More than "occasionally". It's now "usually" :( ** Summary changed: - Crash in ucsi_acpi_async_write [ucsi_acpi] occasionally prevents booting + Crash in ucsi_acpi_async_write [ucsi_acpi] prevents booting ** Summary changed: - Crash in ucsi_acpi_async_write [ucsi_acpi] prevents booting + Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works -- 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/2025120 Title: Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting, while 6.2.0-21 always works Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+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 2025560] Re: lubuntu does not boot after upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
Same problem here with lubuntu 22.04. Last night I did the updates Unfortunately, as of today I cannot boot either in the new 5.19 lowlatency nvidia or 5.15.0.76 generic or anywhere else I can enter safe mode, but do not know what to do there When trying to boot in 5.19 the attached img appears and halts When trying to boot in 5.15, the system just halts - blank screen ** Attachment added: "IMG_20230703_003916.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683464/+files/IMG_20230703_003916.jpg -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
** Attachment added: "IMG_20230703_003916.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683463/+files/IMG_20230703_003916.jpg -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1
[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
yes i tried that. but even with the old kernel, the second monitor did not work. but chrome was running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
When booting just select an older kernel - and hope that the maintainers are quickly cleaning the mess -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
the same. The second monitor does not work, chrome does not start. what do you advise to do? wait or reinstall the system? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2025572] [NEW] Broadcom Wireless Drivers do not install properly as of Ubuntu 22.04
Public bug reported: When installing Broadcom Wireless driver (bcmwl-kernel-source) the package does not properly force the updating of the kernel module blacklist, and as a result the system still loads a conflicting driver (bcma). Users need to manually call the command: sudo update-initramfs -u Which correctly updates the blacklist allowing the Wireless adapter driver to load. On ubuntu versions 20.04 and earlier, installing the driver allows the network card to work immediately (no reboot require, it even works on the USB live distro). For version 22 and 23, it's possible to get it working by manually removing the b43 and bcma drivers, and then adding the wl driver, or running the above command. I'm filing this bug at the suggestion of an Ubuntu member who suggested that the bcmwl-kernel-source package should probably already be performing the update-initramfs command as part of it's installation. See Ubuntu Forums thread: https://ubuntuforums.org/showthread.php?t=248=2=14148921#post14148921 for more detail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: veleek 816 F wireplumber /dev/snd/controlC0: veleek 816 F wireplumber /dev/snd/seq:veleek 814 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Jul 2 15:19:26 2023 InstallationDate: Installed on 2023-06-30 (2 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Hewlett-Packard HP t620 Quad Core TC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=4c92a210-5f47-45e3-9ef4-fda0ed5c04a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-24-generic N/A linux-backports-modules-6.2.0-24-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2015 dmi.bios.release: 2.10 dmi.bios.vendor: AMI dmi.bios.version: L40 v02.10 dmi.board.name: 21B4 dmi.board.vendor: Hewlett-Packard dmi.board.version: A01 dmi.chassis.asset.tag: MXL62112RC 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:bvnAMI:bvrL40v02.10:bd07/03/2015:br2.10:svnHewlett-Packard:pnHPt620QuadCoreTC:pvr:rvnHewlett-Packard:rn21B4:rvrA01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuX1Y83UP#ABA: dmi.product.family: 103C_53302C G=D dmi.product.name: HP t620 Quad Core TC dmi.product.sku: X1Y83UP#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Broadcom Wireless Drivers do not install properly as of Ubuntu 20.X + Broadcom Wireless Drivers do not install properly as of Ubuntu 22.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/2025572 Title: Broadcom Wireless Drivers do not install properly as of Ubuntu 22.04 Status in linux package in Ubuntu: New Bug description: When installing Broadcom Wireless driver (bcmwl-kernel-source) the package does not properly force the updating of the kernel module blacklist, and as a result the system still loads a conflicting driver (bcma). Users need to manually call the command: sudo update-initramfs -u Which correctly updates the blacklist allowing the Wireless adapter driver to load. On ubuntu versions 20.04 and earlier, installing the driver allows the network card to work immediately (no reboot require, it even works on the USB live distro). For version 22 and 23, it's possible to get it working by manually removing the b43 and bcma drivers, and then adding the wl driver, or running the above command. I'm filing this bug at the suggestion of an Ubuntu member who suggested that the bcmwl-kernel-source package should probably already be performing the update-initramfs command as part of it's installation. See Ubuntu Forums thread: https://ubuntuforums.org/showthread.php?t=248=2=14148921#post14148921 for more detail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: veleek 816 F wireplumber /dev/snd/controlC0: veleek 816 F wireplumber /dev/snd/seq:
[Kernel-packages] [Bug 2025568] Re: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
No, this is a Linux only system, but something else clashed. More details: System was tested with kernel mainline 6.3.7 and 6.4.0 Reverting the patch files => Didn't helped (rmmod/modprobe and reboot) Tried original Ubuntu 6.2.0 kernel and this worked again. Removed mainline kernels and reinstalled 6.4.0 which now worked with old firmware package (20230323.gitbcdcfbcf-0ubuntu1) Reinstall new firmware package and it works now with mainline kernel 6.4.0 Second thoughts: As you can see above last working boot was 16:27:57, and this was already a boot with kernel 6.4.0 and latest firmware package 20230629 (I overlooked this one). But I remember now, I was shortly away after boot and the system was going into sleep. After wake-up the system freezed and I rebooted at 16:55:52 and after this reboot mt7921e failed. So, the issue could be the sleep mode. :-/ So, the issue can be closed. Thanks. -- 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/2025568 Title: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921 Status in linux-firmware package in Ubuntu: Invalid Bug description: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025568/+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 2025568] Re: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/2025568 Title: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921 Status in linux-firmware package in Ubuntu: Invalid Bug description: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025568/+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 2025568] Re: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
Is Windows installed on this computer? -- 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/2025568 Title: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921 Status in linux-firmware package in Ubuntu: New Bug description: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025568/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I'm seeing the same thing running Slack. --- [** ~]$ /bin/slack [64844:0702/180844.731816:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped) --- This started after the latest 'apt update/upgrade' The 2nd monitor connected to the laptop this is running is also no longer working. From previous posts, they appear related -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2025568] [NEW] After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
Public bug reported: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/2025568 Title: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921 Status in linux-firmware package in Ubuntu: New Bug description: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025568/+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 2025560] Re: lubuntu does not boot after upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2025560 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. (Given you clearly state you cannot boot with the new kernel(s), please run the command using the older kernel on your actual hardware you mention you can boot with, and clearly indicate (via comment) which kernel you cannot boot & that you're reporting your issue with ) -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
i also have/had this problem. ThinkPad P14s 3rd gen (21J6) with AMD Ryzen 7 pro 6850u with Radeon Graphics. Ubuntu 22.04. Kernel was 5.19.0-46-generic. Those solutions did not work: - no "Sleep Mode" option in my BIOS - did not manage to successfully access the Lenovo advanced BIOS menu to switch from Modern Standby power to S3 (the apparently secret advanced BIOS settings) - turned off "security chip" and secure boot in the BIOS - disabled Wayland What did work was to switch to kernel 6.12.14-060214-generic on Ubunutu 22.04 (#14). Now the suspend/wakeup cycle works. Laptop seems cool/normal and quiet for now. I did not try the amdgpu-install (#8). I do have the issue where "there is a short moment where the plain screen content is visible after wake up, but the screen is locked almost immediately." However, I can live with that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2025538] Re: Unrequested kernel update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-nvidia-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 2025560] Re: lubuntu does not boot after upgrade
Same issue here - after an upgrade to my Ubuntu 22.04.2 LTS installation (not lubuntu), the system either does not boot anymore, or it can load older kernels but without the proprietary nvidia driver loaded. -- 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/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: New Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1
[Kernel-packages] [Bug 2025561] [NEW] crash after installing kernel 5.19.0-1028-lowlatency and nvidia 470
Public bug reported: nvidia manager seems to not recognize my GT660 resolution is like xorg driver 1024 x 768 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-470 470.199.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-1028.29~22.04.1-lowlatency 5.19.17 Uname: Linux 5.19.0-1028-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 13:39:55 2023 InstallationDate: Installed on 2020-11-06 (967 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to jammy on 2022-08-21 (314 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2025561 Title: crash after installing kernel 5.19.0-1028-lowlatency and nvidia 470 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: nvidia manager seems to not recognize my GT660 resolution is like xorg driver 1024 x 768 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-470 470.199.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-1028.29~22.04.1-lowlatency 5.19.17 Uname: Linux 5.19.0-1028-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 13:39:55 2023 InstallationDate: Installed on 2020-11-06 (967 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to jammy on 2022-08-21 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2025561/+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 2025560] [NEW] lubuntu does not boot after upgrade
Public bug reported: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. >From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image-5. 17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0-10 26.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1 hhs-`/syyssyy:-yh WM: Openbox hhs `:/+ossyyhyys -y Theme: Arc-Darker [GTK3] hhy/ `syyysshh: :yhhs Icons: Adwaita [GTK3]
[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Coming back to this report here: as expected but now confirmed: when I boot the old kernel everything is working normally. So the cause is *confirmed* to be the different/upgraded kernel that was installed without my request (as described in https://bugs.launchpad.net/ubuntu/+source/linux-signed- nvidia-5.19/+bug/2025538 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I just checked the chromium bug tracker: the link is valid, but it is flagged as "Only users with EditIssue permission or issue reporter may view.". I guess it's caused by being created from an uploaded crash report. Probably due to privacy considerations as the crash dump might contain private information. There's also no way that I can change the permissions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I get "permission denied" on the chrome bug link https://bugs.chromium.org/p/chromium/issues/detail?id=1459821. Is there a public link for that bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+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
