GNOME Bugzilla – Bug 748462
gdm crashes with proprietary nvidia drivers
Last modified: 2018-05-24 11:11:13 UTC
Hi, first off, I'm using an up to date ArchLinux with gdm 3.16.1.1. What I did: I had nvidia, nvidia-libgl and the 32 bit equivalents installed. I updated the whole system today to the version named above, typed "reboot" and waited. After booting I was greeted with "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again.". (Before login. Pressing that button thus yielded nothing of course.) After replacing the nvidia package with nouveau I got the same result but this time it at least used both screens for it :) Replacing nvidia-libgl with mesa-libgl then solved the problem. Here some except from IRC: Jasper sils_, if we detect that Wayland isn't working properly, we should fall back to the Xorg gdm implementation. Is that not working? sils_ Jasper, it just showed "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." sils_, I just assumed that this was the reason and uninstalling all nvidia stuff using nouveau solved the problem Jasper Yeah, it could be that the fallback isn't working properly. Please let me know what debug info I can provide so the issue can be investigated further. I may not be able to provide much in the next few days though I will try.
(In reply to Lasse Schuirmann from comment #0) > Please let me know what debug info I can provide so the issue can be > investigated further. I may not be able to provide much in the next few days > though I will try. Please provide a backtrace of the crashing process from coredumpctl. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance! Also, please enable debugging in /etc/gdm/custom.conf and post journal output ('journalctl') from right before the crash.
mai 01 21:43:56 njord systemd-coredump[855]: Process 819 (gnome-shell) of user 120 dumped core. Stack trace of thread 819: #0 0x00007f7927e2cf65 n/a (libmutter.so.0) #1 0x00007f7927e392f6 n/a (libmutter.so.0) #2 0x00007f7927e608de meta_init (libmutter.so.0) #3 0x0000000000401ee2 main (gnome-shell) #4 0x00007f7925f09710 __libc_start_main (libc.so.6) #5 0x00000000004022c9 n/a (gnome-shell) Stack trace of thread 821: #0 0x00007f7925fc7c3d poll (libc.so.6) #1 0x00007f79264f10fc n/a (libglib-2.0.so.0) #2 0x00007f79264f120c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f79264f1249 n/a (libglib-2.0.so.0) #4 0x00007f7926517975 n/a (libglib-2.0.so.0) #5 0x00007f7926291424 start_thread (libpthread.so.0) #6 0x00007f7925fd0cbd __clone (libc.so.6) Stack trace of thread 822: #0 0x00007f7925fc7c3d poll (libc.so.6) #1 0x00007f79264f10fc n/a (libglib-2.0.so.0) #2 0x00007f79264f1482 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f7926cfa6d6 n/a (libgio-2.0.so.0) #4 0x00007f7926517975 n/a (libglib-2.0.so.0) #5 0x00007f7926291424 start_thread (libpthread.so.0) #6 0x00007f7925fd0cbd __clone (libc.so.6) Stack trace of thread 852: #0 0x00007f7925fcc7f9 syscall (libc.so.6) #1 0x00007f7926535afa g_cond_wait_until (libglib-2.0.so.0) #2 0x00007f79264c5929 n/a (libglib-2.0.so.0) #3 0x00007f79265182e6 n/a (libglib-2.0.so.0) #4 0x00007f7926517975 n/a (libglib-2.0.so.0) #5 0x00007f7926291424 start_thread (libpthread.so.0) #6 0x00007f7925fd0cbd __clone (libc.so.6) Stack trace of thread 853: #0 0x00007f7925fc7c3d poll (libc.so.6) #1 0x00007f79264f10fc n/a (libglib-2.0.so.0) #2 0x00007f79264f120c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f79105c243d n/a (libdconfsettings.so) #4 0x00007f7926517975 n/a (libglib-2.0.so.0) #5 0x00007f7926291424 start_thread (libpthread.so.0) #6 0x00007f7925fd0cbd __clone (libc.so.6) mai 01 21:43:56 njord kernel: gnome-shell[857]: segfault at 14 ip 00007f404d222f65 sp 00007ffe168e4130 error 4 in libmutter.so.0.0.0[7f404d1dc000+109000]
Created attachment 327475 [details] gdm_debug_journalctl The output was too large to post as a comment.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/229.