GNOME Bugzilla – Bug 618623
random gnome-shell hangs when coming back from suspend
Last modified: 2011-08-21 18:41:10 UTC
Created attachment 161052 [details] output of the terminal I have a Dell Mini 9 running Ubuntu 10.04 with this PPA: https://launchpad.net/~ricotz/+archive/testing The shell suspends and resumes correctly maybe 4 times out of 5 or so, but when it "fails", I observe the following symptoms: - You can click the Applications button (it "reacts" to the mouse click), but it doesn't have any effect (it doesn't go into the overlay mode) - You can't use alt-tab switching - You can use Alt+F2 to run a command... once - You can't do any of the above more than once* Then you can switch to another tty (ctrl+alt+F2 for example) and back to the current tty (ctrl+alt+F7 for example). The shell will be partially unfrozen, allowing you to do alt-F2 again (and do a "gnome-shell --replace" or something). I couldn't see anything special in /var/log or .xsession-errors.log This computer has no problems suspending/resuming with a normal gnome session (compiz or metacity).
I have a related problem using Lucid as well. My system cannot recover properly from suspend while running gnome-shell. When my computer wakes up I get the normal password screen with no apparent problems. However, I after entering my password all I get is a blank screen with a mouse that heavily lags as I try to move it around the screen. If I hit 'Ctrl-C' and the terminal happened to be active before the computer was put to sleep, then gnome-shell will quit and my desktop runs without any problems. I am not sure which log would be most helpful to post. If a dev has a recommendation let me know.
Please tell me what kind of information I can provide to properly troubleshoot this.
It's almost certainly a problem with your video drivers - as far as GNOME Shell is concerned, it doesn't even know that your computer has been suspended. I really have no idea how to go about debugging this problem without having access to an affected system. Providing detailed information about your video card (attach your Xorg.log if you are uncertain) may help correlate with other similar problems. (I'm not sure I'd have an idea if I had access either - I only dabble slightly in video driver debugging.)
Created attachment 164233 [details] various system log files My video card is an integrated Intel i915 (I think) - the one that comes with the Dell Mini 9. I think I have noticed something today: this only seems to happen for prolonged sleeps (let's say, over an hour). Repeated sleep/resume tests don't seem to trigger this problem. I hope those logs reveal something useful. Let me know if there's something else I can do.
FWIW, it doesn't seem to affect a normal gnome session with Mutter as the window manager... Thus the problem really seems to be in gnome shell, rather than mutter or clutter (or even the drivers).
(In reply to comment #5) > FWIW, it doesn't seem to affect a normal gnome session with Mutter as the > window manager... Thus the problem really seems to be in gnome shell, rather > than mutter or clutter (or even the drivers). More likely, the more extensive OpenGL drawing that gnome-shell is doing is triggering driver bugs that Mutter alone doesn't. The only other thing I can think of is that maybe your clock is doing funny things on unsuspend. There have been instances where computers jump the clock around unsuspend. This could theoretically upset the animation timing code in hte shell. You might try changing the time forwards and backwards or backwards and forwards while the shell is running and see if you can reproduce problems.
> You might try changing the time forwards and backwards > or backwards and forwards while the shell is running How do I do that (from a terminal, let's say)?
See 'man date'. ;-)
Since you're using lucid, I think overall there has been suspend issues. I've had the same kind of problem with suspend, so I usually quit from gnome-shell before suspending. But it doesn't really solve the problem since I've had normal gnome-session have problems. The display won't turn back on or there might be other issues. Definitely there is some driver problems. I'm using Nvidia proprietary driver 190.
@Owen: I just tired changing the date/time around while the shell was "frozen", no luck. It doesn't thaw it. @Sri: well, no other app causes this. The laptop suspends and resumes without problems 100% of the times when running a normal gnome session with metacity/compiz/mutter. When the shell hangs, doing a ctrl+alt+backspace to kill Xorg or restarting gdm works, for what it's worth.
(In reply to comment #10) > @Owen: I just tired changing the date/time around while the shell was "frozen", > no luck. It doesn't thaw it. I think what Owen meant was to change the date/time around while the shell is _not_ frozen to confirm/discard a timer issue.
I changed the time (±2 mins) using the "time-admin" tool while running the shell. Moving 2 mins into the future doesn't cause problems. Moving 2 mins into the past freezes the mouse cursor but doesn't freeze the shell itself (pressing the Win key animates into overlay mode). These are not the same symptoms as what I saw on unsuspend (frozen shell that doesn't respond to the Win key, mouse cursor OK). The "seconds" spinbutton widget keeps updating every second in the date/time tool, so it seems like GTK hasn't frozen either.
My problem has always been that the screen becomes very funky with artifacts all over the place. It does happen less often using regular GNOME however. It seems to occur after I unlock the screen. Moving time in the fast would cause a freeze, moving two minutes into the past is pretty good shock to the system. The freeze would relate to a network issue since if I recall, packets are usually tagged with UTC time, so the timers get all messed up at that point. That's why we have utilities like ntp which slowly adjusts the time over a period of time or always continues to sync against a time server. X is very network dependent so that is probably the source of your hang. Thanks for performing the tests. I'm still thinking it is a driver/clutter interaction issue. sri
I think bug #635019 might be a duplicate... Also, note that I am still seeing this problem on a different computer (Thinkpad T43p with an AMD M24GL [Mobility FireGL V3200], using the open source radeon drivers), on Ubuntu 10.10 (mutter 2.31.5, gnome-shell 2.31.5). I sadly can't build from jhbuild as I don't have the whole gnome3 stack (gtk 3 etc).
(In reply to comment #14) > I sadly can't build from jhbuild as I don't have the whole gnome3 stack (gtk 3 > etc). Not sure what you mean by this, but the Shell's jhbuild setup contains everything you need, even if you're still using a distribution from last spring (with GNOME 2.30).
Not seeing this anymore with Fedora 15 on all the machines I've tested.