FS#29653 - [gnome-shell] freezes after logging in

Attached to Project: Arch Linux
Opened by Ben Ruijl (revelation60) - Sunday, 29 April 2012, 07:53 GMT
Last edited by Jan de Groot (JGC) - Friday, 09 November 2012, 11:47 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 15
Private No

Details

Description:
After logging in with GDM, I get the normal gnome background and toolbar at the top and then gnome-shell freezes completely and all I can do is move the mouse. I can see that my name is missing on the right, and that a network logo appeared on the bar (strange, because when gnome is working, I don't see this logo). When I switch to TTY-1 and restart gdm, I can login and gnome-shell works again. When I switch back and forth between the console and X again, I get a black screen with a blinking cursor and in TTY-1 the following message:

** (gdm-binary:2250): WARNING **: Failed to acquire org.gnome.DisplayManager
** (gdm-binary:2250): WARNING **: Could not acquire name; bailing out

I have to restart gdm again and never switch back to a terminal for gnome to work.

Additional info:
gnome-shell 3.4.1-2


Steps to reproduce:
Unclear, but the problem *always* happens on one of my computers, and sometimes on the other.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 09 November 2012, 11:47 GMT
Reason for closing:  Fixed
Comment by Krzysztof Tucholski (rabinhood) - Sunday, 29 April 2012, 08:00 GMT
I confirm. Only wallpaper and mouse cursor after logging in. I have the same problem both with ATI open source radeon and with catalyst drivers. Had to switch to xfce. Had no similar troubles with gnome-shell 3.2.
Comment by Ben Ruijl (revelation60) - Sunday, 29 April 2012, 08:07 GMT
I use the closed-source NVIDIA driver, so that seems to rule out graphic drivers.
Comment by JH (centos) - Tuesday, 01 May 2012, 08:28 GMT
Same for me with ATI open source drivers. After login Gnome-Shell freezes, only cursor works. Had to switch to fallback mode.

edit: I do not have this problem anymore. But I did nothing, just updated some packages (which have nothing to do with it, I guess)
Comment by Clément Foucault (turjuque) - Wednesday, 02 May 2012, 02:29 GMT
Same for me with closed-source Nvidia driver.
Gnome shell freezes and my name isn't displayed in the corner of the screen.
If I restart Xorg it works.
Comment by MaxB (bal0r) - Thursday, 03 May 2012, 21:15 GMT
Interesting, i thought it was a problem with my new radeon hd 6850, but it isn't.
Comment by Emil Ivanov (vladev) - Monday, 07 May 2012, 16:46 GMT
I can confirm this as well on two machines - one Dell Vostro laptop with NVIDIA closed driver and one desktop with Intel i7 GPU.
Comment by Ivan Lyapunov (dront78) - Wednesday, 09 May 2012, 08:01 GMT
Same for me on two laptops with nvidia closed source driver an one with intel 945 chipset
switch to console works and restart gdm solves the problem temporary
also removing ~/.nv and /var/lib/gdm/.nv helps with nvidia no lockups for a week
Comment by Teodor (TdR011) - Thursday, 10 May 2012, 08:49 GMT
I have the same problem. It doesn't always crash, it crashes one out of three times. It is not a driver or a DM bug. It had the same problem with slim and lightdm as well as with gdm.
Comment by Ralf Gamillscheg (spidi0815) - Saturday, 12 May 2012, 19:52 GMT
I have the same problem.
Comment by Ivan Lyapunov (dront78) - Tuesday, 22 May 2012, 16:28 GMT
Today I got the lockup when pressing Win for expose and simply pressed again at random during expose effect.
System became locked as described above and gdm restart helps
But I have no chance to repeat this today another time

ArchLinux x86_64, nvidia gt330m laptop, pacman -Suy'ed for today
Comment by Paweł Tomkiel (neonkowy) - Wednesday, 23 May 2012, 05:36 GMT
Same here, one of three times freezes. I'm on x86_64 with intel i945, logging with slim, so it's not only gdm problem.
Comment by Artiom Molchanov (artiom) - Friday, 25 May 2012, 19:31 GMT
I confirm the issue. It doesn't always freezes: one out of three times approx. I can switch to the console where I was trying to kill some user processes to see if something block the session startup, but without success. I found that gnome-session process don't react on different kill signals (-1, -15, etc.)
Comment by Ionut Biru (wonder) - Friday, 25 May 2012, 19:37 GMT
take a look at this bug: https://bugs.freedesktop.org/show_bug.cgi?id=49211
Comment by Artiom Molchanov (artiom) - Saturday, 26 May 2012, 10:24 GMT
Looks like it it what we have. I forget to mention but if I do a gnome-shell restart with Alt-F2 , r it hangs every time.
Comment by Krzysztof Tucholski (rabinhood) - Wednesday, 30 May 2012, 14:26 GMT
I've found the cause, at least in my case. Broken package gcr was responsible for it. Had to reinstall it with pacman with -f flag ("pacman -Sf gcr"). I got useful clues after trying to switch desktop environment manually from another one (in my case from KDE) by entering "gnome-shell --replace" in konsole window. I have no foggiest idea how did gcr become corrupted. I hope it will help at least some of you.
Comment by Ivan Lyapunov (dront78) - Wednesday, 30 May 2012, 16:09 GMT
reinstalling gcr didn't help for me since I did it about month ago recommended on bbs somewhere. however bug is still persist but no often
Comment by Silvan Jegen (Shugyousha) - Saturday, 09 June 2012, 20:23 GMT
I am using gnome-shell 3.4.1-3 but still had it freeze after I used slim to login (only the desktop background was actually loaded before the freeze). Consulting the X logs revealed that gnome-keyring could not find the necessary libgcr- and libgck-library files. It turns out that they should have been included in the gcr package mentioned in the comment above but apparently weren't in my case. Reinstalling the gcr package let me use the new Gnome shell without any problems (and the library files are now in /usr/lib/ as they should have been before). I am not sure if my experience is actually relevant for this bug report but I just wanted to mention that reinstalling the gcr package may help. It did in my case.
Comment by Ionut Biru (wonder) - Saturday, 09 June 2012, 20:40 GMT
they are included in grc package but you have used pacman -Syuf which is wrong
Comment by Silvan Jegen (Shugyousha) - Saturday, 09 June 2012, 21:03 GMT
I reinstalled the package using "pacman -S gcr" and everything worked as expected.
Comment by Artiom Molchanov (artiom) - Monday, 18 June 2012, 19:07 GMT
I reinstalled gcr and do some other things (not related to this bug) like replacing fam with gamin. Now the first log in pass almost every time and the second freezes almost every time.
Comment by Ionut Biru (wonder) - Monday, 18 June 2012, 19:10 GMT
nobody really looks at the link i posted on 25 may?
Comment by Artiom Molchanov (artiom) - Monday, 18 June 2012, 19:25 GMT
It is all about GDM freeze. And the workaround is to put pam_keyinit to optional.
But it is already the case for me and it was never a GDM issue. It shows the main screen with all gnome-shell staff then hangs.
Comment by Martin Schmölzer (mschmoelzer) - Tuesday, 19 June 2012, 18:07 GMT
I'm also affected by this bug. Occurs in irregular intervals when trying to log in. I've tried switching from gdm to kdm, problem still persists.

I've attached a screenshot of gnome-shell in this frozen state.
When the shell does not freeze, I can see the NetworkManager icon having this red circle for a very short amount of time, then it changes to the normal "connected" icon without the red circle.
Could it be possible that the problem is somehow related to NetworkManager?
   gnome-shell-freeze.jpeg (118.9 KiB)
Comment by Ben Ruijl (revelation60) - Tuesday, 19 June 2012, 18:12 GMT
If it is this bug: https://bugs.freedesktop.org/show_bug.cgi?id=49211 (and it probably is), then no, it has nothing to do with NetworkManager.
Comment by Ivan Lyapunov (dront78) - Tuesday, 19 June 2012, 19:39 GMT
Does anyone tried with systemd?
Comment by Clément Foucault (turjuque) - Tuesday, 19 June 2012, 20:08 GMT
Just to say it happens from time to time on Ubuntu aswell with LightDM so this as nothing to do with gdm.
Comment by Martin Schmölzer (mschmoelzer) - Wednesday, 20 June 2012, 15:15 GMT
Today I tried the patch posted in comment 26 of this page: https://bugs.freedesktop.org/show_bug.cgi?id=49211#c26

Re-compiled the kernel with this patch, then logged into Gnome many times - gnome-shell still froze once, so I guess this is some other bug...
Comment by Jonathan De Nil (ulukai) - Wednesday, 11 July 2012, 08:40 GMT
I'm having the same issue. Using SLIM, latest kernel and Gnome-Shell packages. Also getting the network icon although I use rc.conf for network config (fix IP).
Comment by Arch Linux User (archie0) - Wednesday, 11 July 2012, 09:32 GMT
Works fine for me. Using GDM.
Comment by Paweł Tomkiel (neonkowy) - Wednesday, 11 July 2012, 09:57 GMT
It's definitely problem with networkmanager because i haven't seen this issue on some Wi-Fi (like home and my work), and it freezes on new Wi-Fi's or some new cable networks(if i plug them when logging)
Comment by Mike (asphantix) - Wednesday, 22 August 2012, 00:18 GMT
I'm still affected by this bug. The bad thing is I don't know when it happens. But when it happens then just after I logged in with gdm.
Comment by Jan (rhomb) - Monday, 27 August 2012, 17:41 GMT
I'm also affected on a Lenovo T420 with Intel Integrated graphics
Gnome Shell 3.4.2
Comment by Martin (vbmazter) - Monday, 03 September 2012, 11:20 GMT
I reported the same problem on Bugzilla as ID 676759 (https://bugzilla.gnome.org/show_bug.cgi?id=676759). I'm mentioning this here because I also posted debugging information there, and to me it looks like a deadlock within Gnome Shell because of a condition variable. I.e. not dependent on graphics drivers or gdm.
Comment by Artiom Molchanov (artiom) - Monday, 03 September 2012, 12:09 GMT
With the last upgrade (new kernel and nvidia driver + x.org) it starts to freeze during the session, while opening or closing an application. Happened with firefox, calws-mail, gedit. "Success" rate - 2-3 times per day.
gnome-shell top at 100% of CPU during the freeze. Kill of gnome-shell don't resolve the issue. Sometimes switching the screen (to text and back) solves, but sometimes the keyboard don't work. Only mouse.
Comment by Ivan Lyapunov (dront78) - Monday, 10 September 2012, 09:35 GMT
Agree with last comment. Session sometimes is not stable. Also switching between console and gnome sometimes get a black screen.
XBMC working full screen video reproduces this for me very often
Comment by Artiom Molchanov (artiom) - Monday, 10 September 2012, 09:39 GMT
I found the last time that gnome-screensaver blocks the screen and don't unblock it correctly. I removed the package and now seems that all works better, but it is just one day that I test. Could someone try to remove the gnome-screensaver and see if it solves the issue?
Comment by Greg (dolby) - Monday, 15 October 2012, 02:38 GMT
Is this still a problem in 3.6?
Comment by MaxB (bal0r) - Thursday, 01 November 2012, 14:34 GMT
I didn't realise any freezing of my system after die upgrade to Gnome 3.6.
Comment by Ivan Lyapunov (dront78) - Sunday, 04 November 2012, 10:17 GMT
login by "user1"
change user
and login again by "user1"

black screen
Comment by Balló György (City-busz) - Friday, 09 November 2012, 06:55 GMT
It seems that it no longer occurs after I updated to GNOME 3.6.
Comment by Mike (asphantix) - Friday, 09 November 2012, 08:42 GMT
Yes, it seems fixed now with GNOME 3.6

Loading...