FS#51527 - [nvidia] 375.10-1 Breaks KDE Screen Locker & Reboot/Shutdown/etc from the Start Menu
Attached to Project:
Arch Linux
Opened by f (bakgwailo) - Tuesday, 25 October 2016, 00:16 GMT
Last edited by Felix Yan (felixonmars) - Monday, 31 October 2016, 16:08 GMT
Opened by f (bakgwailo) - Tuesday, 25 October 2016, 00:16 GMT
Last edited by Felix Yan (felixonmars) - Monday, 31 October 2016, 16:08 GMT
|
Details
Description:
After upgrading to the NVIDIA Beta driver 375.10-1 in testing, being able to unlock my session in the latest Plasma release is broken. I can enter my password fine, and then it simply looks like it wants to unlock, but it flashes back to the greater with no password in it. loginctl unlock-sessions works from the command line. Also, the reboot/etc buttons are broken in the start menu. The GUI pops up, but selecting an option causes it to seg fault (and the KDE bug reporter to popup). Rolling back to the last stable NVIDIA release (370.28) fixed the issue. I have reproduced this on both my desktop (GTX 970) and laptop (Quadro m2000m). Steps to reproduce: 1) Update to the 375.10-1 driver. 2) Reboot 3) Log into Plasma via SDDM. 4) Either Lock the Screen via the start menu 4a) Try to unlock the screen or 5) Chose reboot 5a) Confirm Either the screen should not unlock and you are presented with the password entry screen again, or, in the case of reboot, it will segfault and the system doesn't reboot. |
This task depends upon
Oct 24 17:29:37 laptop drkonqi[14605]: Sending SIGCONT to process
Oct 24 17:29:37 laptop drkonqi[14605]: garbage detected: "[Thread debugging using libthread_db enabled]\n"
Oct 24 17:29:37 laptop drkonqi[14605]: line "Using host libthread_db library \"/usr/lib/libthread_db.so.1\".\n" did not match
Oct 24 17:29:37 laptop drkonqi[14605]: garbage detected: "0x00007f4faeeceffd in nanosleep () from /usr/lib/libc.so.6\n"
Oct 24 17:29:37 laptop drkonqi[14605]: thread indicator detected: "[Current thread is 1 (Thread 0x7f4fb32b2840 (LWP 14594))]\n"
Oct 24 17:29:37 laptop drkonqi[14605]: thread start detected: "Thread 1 (Thread 0x7f4fb32b2840 (LWP 14594)):\n"
Oct 24 17:29:37 laptop drkonqi[14605]: 0 "nanosleep" "" "/usr/lib/libc.so.6"
Oct 24 17:29:37 laptop drkonqi[14605]: 1 "sleep" "" "/usr/lib/libc.so.6"
Oct 24 17:29:37 laptop drkonqi[14605]: 2 "??" "" "/usr/lib/libKF5Crash.so.5"
Oct 24 17:29:37 laptop drkonqi[14605]: 3 "??" "" "/usr/lib/libKF5Crash.so.5"
Oct 24 17:29:37 laptop drkonqi[14605]: 4 "KCrash::defaultCrashHandler" "" "/usr/lib/libKF5Crash.so.5"
Oct 24 17:29:37 laptop drkonqi[14605]: 6 "pthread_mutex_lock" "" "/usr/lib/libpthread.so.0"
Oct 24 17:29:37 laptop drkonqi[14605]: 7 "??" "" "/usr/lib/libGLX_nvidia.so.0"
Oct 24 17:29:37 laptop drkonqi[14605]: 8 "??" "" "/usr/lib/libGLX_nvidia.so.0"
Oct 24 17:29:37 laptop drkonqi[14605]: 9 "??" "" "/usr/lib/libEGL.so.1"
Oct 24 17:29:37 laptop drkonqi[14605]: 10 "_dl_fini" "" "/lib64/ld-linux-x86-64.so.2"
Oct 24 17:29:37 laptop drkonqi[14605]: 11 "__run_exit_handlers" "" "/usr/lib/libc.so.6"
Oct 24 17:29:37 laptop drkonqi[14605]: 12 "exit" "" "/usr/lib/libc.so.6"
Oct 24 17:29:37 laptop drkonqi[14605]: 13 "__libc_start_main" "" "/usr/lib/libc.so.6"
Oct 24 17:29:37 laptop drkonqi[14605]: 14 "_start" "" ""
Oct 24 17:29:37 laptop drkonqi[14605]: Sending SIGSTOP to process
Oct 24 17:29:37 laptop drkonqi[14605]: 2 "#14 0x0000000000405a1a in _start ()\n"
Oct 24 17:29:37 laptop drkonqi[14605]: 3 "#10 0x00007f4fb31bbae8 in _dl_fini () from /lib64/ld-linux-x86-64.so.2\n"
Oct 24 17:29:37 laptop drkonqi[14605]: 1 "#9 0x00007f4f8e623e89 in ?? () from /usr/lib/libEGL.so.1\n"
Oct 24 17:29:37 laptop drkonqi[14605]: 1 "#8 0x00007f4f97341dc8 in ?? () from /usr/lib/libGLX_nvidia.so.0\n"
Oct 24 17:29:37 laptop drkonqi[14605]: 1 "#7 0x00007f4f9736ae1c in ?? () from /usr/lib/libGLX_nvidia.so.0\n"
Oct 24 17:29:37 laptop drkonqi[14605]: Rating: 12 out of 40 Usefulness: Useless
Oct 24 17:29:37 laptop drkonqi[14605]: 90%: 36 70%: 28 40%: 16
Oct 24 17:29:37 laptop drkonqi[14605]: Have seen stack base: true Lines counted: 4
Which is to say, its probably useless.
https://devtalk.nvidia.com/default/topic/973013/linux/libegl-so-1-libegl-so-375-10-difference-not-in-release-notes-docs/
https://devtalk.nvidia.com/default/topic/972736/linux/some-applications-crash-on-exit-with-nvidia-375-10/
https://github.com/NVIDIA/libglvnd/issues/103#issuecomment-256259387
Solution:
1) libglvnd
a) update libglvnd (commit b78630e) + 110.patch [1] + 97.patch [2]
b) fix makedepends ('libx11' 'glproto' 'libxext' 'python')
c) fix compatibility with older nvidia drivers for bumblebee [3]
(libEGL.so, libEGL.so.1 - symbolic links and libEGL.so.1.0.0)
2) nvidia-utils (nvidia-libgl)
a) fix/add libEGL.* (see 1.c)
b) add 10_nvidia.json (/usr/share/glvnd/egl_vendor.d)
[1] https://patch-diff.githubusercontent.com/raw/NVIDIA/libglvnd/pull/110.patch # fix KDE
[2] https://patch-diff.githubusercontent.com/raw/NVIDIA/libglvnd/pull/97.patch # fix build error - python
[3] https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/libglvnd#n29
Also, lately it seems like the NVIDIA beta drivers are making it into testing (and even stable) repos. I thought only the stable releases should be brought in, with the AUR packages for betas.