FS#31893 - [gnome-session] crashing
Attached to Project:
Arch Linux
Opened by Jan Rüegg (rggjan) - Thursday, 11 October 2012, 07:04 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 17 November 2012, 15:10 GMT
Opened by Jan Rüegg (rggjan) - Thursday, 11 October 2012, 07:04 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 17 November 2012, 15:10 GMT
|
Details
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, the black screen with the "logout" button appears in the foreground. Same thing happens in the forced fallback mode. Starting directly via startx does not help. Starting KDE from GDB is still works. Doing a "gnome-shell --replace" within kde also works. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Saturday, 17 November 2012, 15:10 GMT
Reason for closing: Fixed
Saturday, 17 November 2012, 15:10 GMT
Reason for closing: Fixed
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... In any case, its also reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=685934
But I have to mention that I'm on testing and gnome-unstable.
[EDIT]
Ok after the last update it seems to work now.
You probably have some weird hack on your system because only 2 people are affected.
No this bug doesn't occur for me anymore.
I don't think it was related with 'some weird hack' but maybe with the gnome-unstable repo, but after a few updates (I don't know which it was) the problem was gone.