GNOME Bugzilla – Bug 696035
clutter 1.14 hangs gnome-shell 3.6.x from starting up
Last modified: 2013-08-08 15:38:04 UTC
Clutter/cogl 1.13.8 prevents gdm from starting up. From /var/log/gdm/:0-greeter.log: Window manager warning: Log level 16: Failed to load apps: Failed to look up menu_file for "applications.menu" JS LOG: GNOME Shell started at Sun Mar 17 2013 21:14:36 GMT+0000 (GMT) WARNING: gnome-keyring:: couldn't connect to: /run/user/106/keyring-cLkKQb/pkcs11: No such file or directory failed to create drawable (...) failed to create drawable Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! Window manager warning: Log level 8: g_source_remove: assertion `tag > 0' failed gnome-session[25280]: WARNING: Detected that screensaver has left the bus gnome-session[25280]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed (gnome-settings-daemon:25303): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: The connection is closed (gnome-settings-daemon:25303): GLib-GIO-WARNING **: Error releasing name org.freedesktop.ScreenSaver: The connection is closed After downgrade to 1.12.x the problem was gone.
thanks for your bug report. I am afraid I will need more information as to what happens, given that the log is not helping me in any way. even if downgrading Clutter seems to "fix" this, I'm going to re-assign the bug to GDM in the hope that the maintainer can glean some information from the log, or at least ask the right questions.
unfortunately that log doesn't seem to have much to do with the problem (other than it shows gnome-shell is crashing) i assume startx fails as well? any chance you could get a backtrace?
(In reply to comment #2) > unfortunately that log doesn't seem to have much to do with the problem (other > than it shows gnome-shell is crashing) > > i assume startx fails as well? any chance you could get a backtrace? All debug symbols are installed. However I'm a little bit (~5 years) out of date with gnome session startup. What programs do you want to run, under which account and with what parameters?
can you log in with working clutter, update your clutter,then open up a terminal and run $ screen $ script $ gdb --args gnome-shell --replace (gdb) run THe problem should reproduce. Switch to a text vt with e.g. ctrl-alt-f3, log in, and run screen -rd to get access to the gdb prompt. Is it crashed? are there any messages on the screen? If it's crashed run: (gdb) thread apply backtrace full When it's all said and done there should be a log file called typescript that has the messages in it.
(In reply to comment #4) > $ gdb --args gnome-shell --replace It looks like gnome-shell doesn't segfault's. The stacktracke of gnome-shell from gdm session is attached below - I got the same results from replacing gnome-shell from inside session. gjs_callstack is empty. Continuing. [Thread 0x7f7464fa1700 (LWP 14268) exited] Program received signal SIGINT, Interrupt. 0x00007f748d25a27d in poll () at ../sysdeps/unix/syscall-template.S:81 81 in ../sysdeps/unix/syscall-template.S
+ Trace 231666
I've got reproduction with gtk+ 3.8, clutter/cogl 1.14 and gdm/gnome-shell 3.6.x.
As additional information - in user session the hang is triggered by the overlay mode. The display is not hanged (i.e. the changes inside windows are still redrawn) but it is not possible to get outside the overlay etc. There are no additional errors printed (I got error about calendar but it was present when I downgraded the clutter). The gtk+ 3.8 + clutter/cogl 1.12 does not trigger the behaviour.
The problem does not occur with gdm+gnome-shell 3.8.
Not reproduced anymore + no duplicates.