Bug#706457: gnome-shell hangs often when trying to unlock

[Praveen A]

package: gnome-shell
severity: critical
version: 3.8.1-2

I have to keep restarting X to continue working after it hangs. Log
message below. I ran gnome-shell --replace >gnome-shell-log.2 2>&1 to
capture this.

It happens when trying to unlock by pushing first lock screen up.

      JS LOG: IBus version is too old
      JS LOG: GNOME Shell started at Tue Apr 30 2013 17:11:10 GMT+0530 (IST)
    JS ERROR: !!!   Error getting systemd inhibitor
    JS ERROR: !!!     message =
'"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send
message, 2 matched rules; type="method_call", sender=":1.132" (uid=500
pid=5622 comm="gnome-shell --replace ")
interface="org.freedesktop.login1.Manager" member="Inhibit" error
name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=1340
comm="/lib/systemd/systemd-logind ")"'
    JS ERROR: !!!     fileName =
'"/usr/share/gnome-shell/js/misc/loginManager.js"'
    JS ERROR: !!!     lineNumber = '227'
    JS ERROR: !!!     stack = '"0 anonymous("result" = [object
GObject_Object], "proxy" = [object
GObject_Object])@/usr/share/gnome-shell/js/misc/loginManager.js:227
"'
ജാലക പാലകന്റെ മുന്നറിയിപ്പ്:‌Log level 16: gnome-shell: Fatal IO error
0 (Success) on X server :0.

Before gnome 3.8 also it used to happen, but at that time I could
either kill gnome-screensaver or gnome-shell from a text console to
get back to previous stage. Killing gnome-shell used to restart it in
earlier versions, but it not the same now. Also there is no separate
gnome-screensaver process now to kill.
--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
You have to keep reminding your government that you don't get your
rights from them; you give them permission to rule, only so long as
they follow the rules: laws and constitution.