Public bug reported: I'm running MATE desktop and I installed NVIDIA GTX 1060 GPU to my system and Xorg crashes after entering password.
I proceeded to run strace with startx trying to debug this and it seems that the window manager `marco` does some (yet unknown) command which causes Xorg to crash with SIGABRT (signal 6) or SIGSEGV (signal 11) and emit stack trace: 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 2: ? (?+0x0) (EE) Segmentation fault at address 0x0 (EE) Caught signal 11 (Segmentation fault). Server aborting The Xorg itself declares signal 11 but `journalctl --since "5 min ago"` shows kernel: potentially unexpected fatal signal 6. kernel: CPU: 2 PID: 20660 Comm: Xorg Tainted: P OE 5.15.0-53-lowlatency #59~20.04.1-Ubuntu kernel: Hardware name: System manufacturer System Product Name/P8H77-M PRO, BIOS 1505 10/17/2014 followed with register dump. Before crashing, process running `marco` also emits warning which I think is not related to the problem (it may be caused by the fact that I executed marco with startx instead of mate-session): Window manager warning: Log level 128: Name com.canonical.AppMenu.Registrar does not exist on the session bus Workaround: downgrading to NVIDIA driver version 470 avoids the problem (as suggested here: https://ubuntu-mate.community/t/updated-nvidia-settings-now-x-wont-start/24991) # sudo apt install linux-modules-nvidia-470-lowlatency-hwe-20.04 nvidia- driver-470 linux-modules-nvidia-520-lowlatency-hwe-20.04- nvidia- driver-520- I also tried version 515 and it caused the same crash. I'm using following kernel package: linux-lowlatency-hwe-20.04 (+ linux- tools-lowlatency-hwe-20.04) I would guess that the bug is in Xorg OsLookupColor() implementation which gets triggered by recent NVIDIA driver change. Bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853266 might be related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-520 (not installed) ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-lowlatency 5.15.64 Uname: Linux 5.15.0-53-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Nov 26 21:42:50 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-520 UpgradeStatus: Upgraded to focal on 2022-09-13 (74 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 ** Affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1998024 Title: Xorg crashes on startup if Marco window manager is used Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: I'm running MATE desktop and I installed NVIDIA GTX 1060 GPU to my system and Xorg crashes after entering password. I proceeded to run strace with startx trying to debug this and it seems that the window manager `marco` does some (yet unknown) command which causes Xorg to crash with SIGABRT (signal 6) or SIGSEGV (signal 11) and emit stack trace: 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 2: ? (?+0x0) (EE) Segmentation fault at address 0x0 (EE) Caught signal 11 (Segmentation fault). Server aborting The Xorg itself declares signal 11 but `journalctl --since "5 min ago"` shows kernel: potentially unexpected fatal signal 6. kernel: CPU: 2 PID: 20660 Comm: Xorg Tainted: P OE 5.15.0-53-lowlatency #59~20.04.1-Ubuntu kernel: Hardware name: System manufacturer System Product Name/P8H77-M PRO, BIOS 1505 10/17/2014 followed with register dump. Before crashing, process running `marco` also emits warning which I think is not related to the problem (it may be caused by the fact that I executed marco with startx instead of mate-session): Window manager warning: Log level 128: Name com.canonical.AppMenu.Registrar does not exist on the session bus Workaround: downgrading to NVIDIA driver version 470 avoids the problem (as suggested here: https://ubuntu-mate.community/t/updated-nvidia-settings-now-x-wont-start/24991) # sudo apt install linux-modules-nvidia-470-lowlatency-hwe-20.04 nvidia-driver-470 linux-modules-nvidia-520-lowlatency-hwe-20.04- nvidia-driver-520- I also tried version 515 and it caused the same crash. I'm using following kernel package: linux-lowlatency-hwe-20.04 (+ linux-tools-lowlatency-hwe-20.04) I would guess that the bug is in Xorg OsLookupColor() implementation which gets triggered by recent NVIDIA driver change. Bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853266 might be related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-520 (not installed) ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-lowlatency 5.15.64 Uname: Linux 5.15.0-53-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Nov 26 21:42:50 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-520 UpgradeStatus: Upgraded to focal on 2022-09-13 (74 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1998024/+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
