GNOME Bugzilla – Bug 685934
Crashing upon login
Last modified: 2015-01-10 13:01:59 UTC
Since yesterday, the gnome shell is crashing whenever logging in from GDM. I just get the mouse and the wallpaper, and after quite a long time, the "oh no, something has gone wrong - log out" message appears. Pressing the windows button still opens the overview. Also, opening new programs in the ovieview works, but as soon as the overview is left (selecting a window), the black screen with the "logout" button appears in the foreground. Forced fallback mode doesn't work either. Starting directly via startx does not help. Starting KDE from GDB is still works. Doing a "gnome-shell --replace" within kde also works. Any possibilty to check what triggers this strange error window?
Which distribution is this, and which updates did your distribution install yesterday? :) Also see https://live.gnome.org/GnomeShell/Debugging
Sorry, I forgot to mention that. I'm running archlinux 64-bit, with all up-to-date packages: extra/gnome-session 3.4.2-3 (gnome) extra/gnome-shell 3.4.2-1 (gnome) ... I have seen the Debugging article. However, this doesn't really help since the gnome shell does NOT crash, and therefore no backtrace on the gnome-shell binary can be generated. Everything actually seems to work fine in the background except the window telling me that something went wrong :) Upgrades before the reboot that didn't work anymore: [2012-10-09 17:01] upgraded chromium (22.0.1229.79-2 -> 22.0.1229.92-1) [2012-10-09 17:01] upgraded flashplugin (11.2.202.238-1 -> 11.2.202.243-1) [2012-10-09 17:01] upgraded gcc-libs (4.7.1-6 -> 4.7.2-1) [2012-10-09 17:01] upgraded gcc (4.7.1-6 -> 4.7.2-1) [2012-10-09 17:01] upgraded gstreamer0.10-bad (0.10.23-2 -> 0.10.23-3) [2012-10-09 17:01] installed opus (1.0.1-2) [2012-10-09 17:01] upgraded gstreamer0.10-bad-plugins (0.10.23-2 -> 0.10.23-3) [2012-10-09 17:01] upgraded iputils (20101006-4 -> 20101006-7) [2012-10-09 17:01] upgraded libltdl (2.4.2-6 -> 2.4.2-7) [2012-10-09 17:01] upgraded libtool (2.4.2-6 -> 2.4.2-7) [2012-10-09 17:01] upgraded linux-api-headers (3.5.1-1 -> 3.5.5-1) [2012-10-09 17:01] upgraded linux-ck-corex (3.5.5-1 -> 3.5.6-1) [2012-10-09 17:01] upgraded linux-ck-corex-headers (3.5.5-1 -> 3.5.6-1) [2012-10-09 17:01] upgraded linux-headers (3.5.5-1 -> 3.5.6-1) [2012-10-09 17:01] upgraded net-snmp (5.7.1-3 -> 5.7.1-4) [2012-10-09 17:45] upgraded dkms-bbswitch (0.4.2-1 -> 0.4.2-1) [2012-10-09 18:08] upgraded lib32-gcc-libs (4.7.1-6 -> 4.7.2-1) [2012-10-09 22:29] removed vdpau-video (0.7.3-3) [2012-10-09 22:29] upgraded hplip (3.12.9-2 -> 3.12.10-1) [2012-10-09 22:29] upgraded lib32-dbus-core (1.6.4-1 -> 1.6.8-1) [2012-10-09 22:29] upgraded lib32-libtiff (4.0.2-1 -> 4.0.3-1) [2012-10-09 22:29] upgraded xcb-proto (1.7.1-1 -> 1.8-1) [2012-10-09 22:29] upgraded libxcb (1.8.1-1 -> 1.9-1) [2012-10-09 22:29] upgraded lib32-libxcb (1.8.1-2 -> 1.9-1) [2012-10-09 22:29] upgraded libva (1.1.0-1 -> 1.1.0-2) [2012-10-09 22:29] installed libva-vdpau-driver (0.7.4-1) I could also generate a xsession-errors file with gnome-session running in --debug mode. Would that help?
Just found the solution (or more a workaround), after about 12 hours of searching and a complete system reinstall: The problem occurs when enabling the NetworkManager with [code] $ sudo systemctl enable NetworkManager.service ln -s '/usr/lib/systemd/system/NetworkManager.service' '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' ln -s '/usr/lib/systemd/system/NetworkManager.service' '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' [/code] The two services seem to conflict somehow, and the gnome session cannot start anymore. When removing the multi-user target [code] $ sudo rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' [/code] Everything works just fine, and I can login again! I don't really know now, if the bug is within gnome-session, networkmanager or systemd...
Most likely a duplicate of bug 687570. There's a debug patch in the downstream bug if you could check it: https://bugs.archlinux.org/task/32456
Jan: Could you check the debug patch in comment 4?
(In reply to comment #5) > Jan: Could you check the debug patch in comment 4? Hi Jan, I am closing this bug report as no updated information has been provided. Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.