GNOME Bugzilla – Bug 706688
Gnome 3 freezes after login screen
Last modified: 2020-11-15 14:17:50 UTC
Gnome 3 freezes after login screen. I am using lightdm on Ubuntu 13.04. Can someone tell me where should I find logs or other debugging information?
Hardware Zenbook Prime Touch UX31A using Intel® Core™ i5-3317U processor which integrates Intel® HD Graphics 4000 graphics card.
Created attachment 252953 [details] Last 100 linnes from Xorg.0.log
Created attachment 252954 [details] Last 100 linnes from Xorg.1.log
After installing Intel Graphics from https://01.org/linuxgraphics/ the problem persists.
I found the circumstance that creates this problem: I am using a second screen. When I don't use the second screen there is no problem. I normally use the second screen connected via HDMI. I also tried the second screen via VGA but the problem was still there. I found a workaround: Unplug the cable until after I log in and reconnect it afterwards. Any idea on how to further investigate this?
I tried to install Ubuntu without the second screen. The problem still persists when I reconnect it before turning on the computer.
Does the same happen with unity? If you start with unity and run gnome-shell --replace from a terminal, does it freeze? Also, can you find relevant info from ~/.xsession-errors? Don't post all of it, as it contains the output of all you session processes, just look for "Window manager warning" and "gnome-shell"
@Giovanni Campagna - "Does the same happen with unity?" - No - "If you start with unity and run gnome-shell --replace from a terminal, does it freeze?" - This is not working. I get the following error message: % gnome-shell -r org.gnome.Shell already exists on bus and --replace not specified - "Also, can you find relevant info from ~/.xsession-errors?" - I turned on the computer with the second screen connected. I logged in and after it freezed I pressed Ctrl+Alt+F6 and collected the following contents of .xsession-errors: Script for cjkv started at run_im. Script for default started at run_im. Script for cjkv started at run_im. Script for default started at run_im. JS LOG: IBus version is too old (nautilus:2092): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed (nautilus:2092): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed ** (nautilus:2092): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:2092): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:2092): WARNING **: Can not get _NET_WORKAREA ** (nautilus:2092): WARNING **: Can not determine workarea, guessing at layout JS LOG: GNOME Shell started at Mon Aug 26 2013 17:21:45 GMT+0300 (EEST) failed to create drawable ** (nautilus:2092): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:2092): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:2092): WARNING **: Can not get _NET_WORKAREA ** (nautilus:2092): WARNING **: Can not determine workarea, guessing at layout
I guess the interesting line is "failed to create drawable" Texture limits exceeded? Seems unlikely for Ironlake... (I wonder why we keep creating a screen-sized texture, and where...)
Gnome 3 freezes instantly after I log in. The top black bar of Gnome 3 is still visible when it freezes. I noticed that if I reconnect the second screen after I get the lightdm login prompt it doesn't freeze.
Are you still experiencing this issue?
Created attachment 366575 [details] Xorg logs / xsession errors
Hi Alexandre, I have a similar issue and was looking in the Ubuntu bug tracker, I found this: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458 The issue exists since a long time. But I have a black screen only for 20-30s then disk activity and desktop is ready to be used. There's some kind of timeout but I don't know how to find out what it is. Maybe we could keep this bug for "freeze after login" and use this bug number for the Ubuntu team as reference? If I can provide any information that could help narrow down the issue, feel free to ask. Regards, Régis (sorry for the bug mail, long time since the last time I did use bugzilla)
(In reply to RC from comment #12) > Created attachment 366575 [details] > Xorg logs / xsession errors There's no gnome-shell output in there. Also are you sure that you are still using a Ubuntu version with upstart instead of systemd? In that case, your distro is likely too old to be relevant to upstream.
Hi Florian, I'm using the last version of ubuntu, up to date. Someone helped debugging the issue on launchpad and the issue is due to gnome-screensaver: janv. 10 07:54:48 hephaistos gnome-session[2639]: gnome-session-binary[2639]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente est dépassé janv. 10 07:54:48 hephaistos gnome-session-binary[2639]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente est dépassé janv. 10 07:54:48 hephaistos gnome-screensav[2776]: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files janv. 10 07:54:48 hephaistos dbus-daemon[2632]: Successfully activated service 'org.gnome.ScreenSaver' I did remove the package "gnome-screensaver" and my login delay is no longer here. The associated ubuntu bug is https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011 Regards,
(In reply to RC from comment #15) > I'm using the last version of ubuntu, up to date. Then you should be using systemd, which means that logs are in the journal (see man journalctl for example) - any errors and warnings from your GNOME session should be logged there nowadays rather than to xsession-errors > Someone helped debugging the issue on launchpad and the issue is due to > gnome-screensaver Eeeeks, gnome-screensaver was retired in GNOME 3.6 five(!) years ago :-(
> Eeeeks, gnome-screensaver was retired in GNOME 3.6 five(!) years ago :-( So someone did mess up in the "automated system upgrade" I assume. The package should probably be removed https://packages.ubuntu.com/source/artful/gnome-screensaver :/
Closing as gnome-shell is not involved per previous comments