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 692356 - gnome-shell periodically hangs after "screensaver left the bus" message in .cache/gdm/session.log
gnome-shell periodically hangs after "screensaver left the bus" message in .c...
Status: RESOLVED DUPLICATE of bug 688197
Product: gnome-shell
Classification: Core
Component: lock-screen
3.6.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-01-23 06:13 UTC by Wolfram
Modified: 2013-01-24 08:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace after hang (34.46 KB, text/plain)
2013-01-24 07:44 UTC, Wolfram
Details

Description Wolfram 2013-01-23 06:13:06 UTC
After update to gnome 3.6 I've noticed that gnome-shell periodically (5-10 times during work day) hangs without any message and only "killall -9 gnome-shell" helps.

So, I've noticed that in all the cases last message in session log is 

gnome-session[3092]: WARNING: Detected that screensaver has left the bus

Previous messages always looks not related to problem.
So, maybe some kind of shell watchdog should be introduced to restart hung shell automatically?


wolfy@zen ~ % cat .cache/gdm/session.log | grep -B 10  killed    
"'
      JS LOG: loading default theme (Adwaita)
      JS LOG: Ignored reply to dbus method: (new Number(30))

(gnome-shell:3249): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)

(gnome-shell:3249): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)

(gnome-shell:3249): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
gnome-session[3092]: WARNING: Detected that screensaver has left the bus
gnome-session[3092]: WARNING: Application 'gnome-shell.desktop' killed by signal 9
--
(evince:7318): Gtk-WARNING **: Theme parsing error: epiphany.css:13:17: Not using units is deprecated. Assuming 'px'.

(evince:7318): Gtk-WARNING **: Theme parsing error: epiphany.css:160:17: Not using units is deprecated. Assuming 'px'.

(gnome-shell:5206): Cogl-WARNING **: Over 50 separate fragment shaders have been generated which is very unusual, so something is probably wrong!


(gnome-shell:5206): Cogl-WARNING **: Over 50 separate programs have been generated which is very unusual, so something is probably wrong!

gnome-session[3092]: WARNING: Detected that screensaver has left the bus
gnome-session[3092]: WARNING: Application 'gnome-shell.desktop' killed by signal 9
Comment 1 Giovanni Campagna 2013-01-23 15:05:10 UTC
Are you sure that the message "screensaver has left the bus" happens before you kill the shell?
That message is logged by gnome-session when the shell disconnects from the bus, which almost surely happens only for a crash.

It would be very helpful you could attach a gdb during a hang, and report us a backtrace.
Comment 2 Wolfram 2013-01-23 16:24:12 UTC
No, not sure.

What about gdb trace - I'll try (but I not sure that my binaries have debug information)
Comment 3 Wolfram 2013-01-24 07:44:23 UTC
Created attachment 234276 [details]
backtrace after hang
Comment 4 Giovanni Campagna 2013-01-24 08:36:48 UTC
Ok, so this is the usual hang at garbage collection time.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 688197 ***