After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 706688 - Gnome 3 freezes after login screen
Gnome 3 freezes after login screen
Status: RESOLVED INVALID
Product: gnome-shell
Classification: Core
Component: general
3.8.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-08-23 20:00 UTC by aalexgabi
Modified: 2020-11-15 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Last 100 linnes from Xorg.0.log (8.01 KB, text/plain)
2013-08-23 20:51 UTC, aalexgabi
Details
Last 100 linnes from Xorg.1.log (5.45 KB, text/plain)
2013-08-23 20:52 UTC, aalexgabi
Details
Xorg logs / xsession errors (5.85 KB, application/zip)
2018-01-09 19:16 UTC, RC
Details

Description aalexgabi 2013-08-23 20:00:56 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?
Comment 1 aalexgabi 2013-08-23 20:08:49 UTC
Hardware Zenbook Prime Touch UX31A using Intel® Core™ i5-3317U processor which integrates Intel® HD Graphics 4000 graphics card.
Comment 2 aalexgabi 2013-08-23 20:51:53 UTC
Created attachment 252953 [details]
Last 100 linnes from Xorg.0.log
Comment 3 aalexgabi 2013-08-23 20:52:18 UTC
Created attachment 252954 [details]
Last 100 linnes from Xorg.1.log
Comment 4 aalexgabi 2013-08-23 21:46:49 UTC
After installing Intel Graphics from https://01.org/linuxgraphics/ the problem persists.
Comment 5 aalexgabi 2013-08-23 23:41:44 UTC
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?
Comment 6 aalexgabi 2013-08-24 14:37:04 UTC
I tried to install Ubuntu without the second screen. The problem still persists when I reconnect it before turning on the computer.
Comment 7 Giovanni Campagna 2013-08-26 12:10:14 UTC
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"
Comment 8 aalexgabi 2013-08-26 14:43:38 UTC
@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
Comment 9 Giovanni Campagna 2013-08-26 14:47:35 UTC
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...)
Comment 10 aalexgabi 2013-08-26 14:49:50 UTC
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.
Comment 11 Alexandre Franke 2017-11-01 14:54:14 UTC
Are you still experiencing this issue?
Comment 12 RC 2018-01-09 19:16:11 UTC
Created attachment 366575 [details]
Xorg logs / xsession errors
Comment 13 RC 2018-01-09 19:17:04 UTC
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)
Comment 14 Florian Müllner 2018-01-11 16:04:29 UTC
(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.
Comment 15 RC 2018-01-11 16:10:04 UTC
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,
Comment 16 Florian Müllner 2018-01-11 16:16:09 UTC
(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 :-(
Comment 17 RC 2018-01-11 16:25:57 UTC
> 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 :/
Comment 18 André Klapper 2020-11-15 14:17:50 UTC
Closing as gnome-shell is not involved per previous comments