GNOME Bugzilla – Bug 697170
gnome-shell freeze
Last modified: 2013-04-06 00:23:44 UTC
Created attachment 240473 [details] Backtrace gnome-shell randomly freezes (or crashs?) about every 2 or 3 days for me. This is a backtrace of the last one. I didn't do anything special was happening at the time of the freeze. The freezes do not appear to be buggy opengl drivers, as I can always kill -9 the gnome-shell process and start a new one which works then. I created a backtrace as described here at https://live.gnome.org/GnomeShell/Debugging it is attached to this report. Not that trying to get a javascript backtrace did not work, gdb simply froze as well until I hit CTRL+C. I'm running Ubuntu 12.10 with the distribution provided gnome packages which is gnome-shell-3.6.2-0ubuntu0.2.
I'm having this same issue. I'm running the latest from the Gnome 3 PPA in Ubuntu 12.10. The gnome-shell process seemingly randomly freezes once or twice per day. When this happens, I can move the mouse around the screen, but nothing responds or updates. The clock and all windows are frozen and don't update. I can switch to another terminal using Ctrl-Alt-F1. If I switch back to terminal 7, the screen is black with just a mouse pointer that I can move around. I can fix the problem by killing the gnome-shell process (have to use kill -9), which restarts the process and causes the UI to become responsive again when I switch back to terminal 7. There is nothing in any of my system logs that seems to indicate any type of a problem. The next time it happens, I can submit a backtrace if that would be helpful.
Created attachment 240748 [details] Backtrace 2 stderr of gnome-shell can be found in the xsession-errors log
Created attachment 240749 [details] xsession errors containing the gnome-shell javascript backtrace at the end
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 670200 ***