Your message dated Tue, 18 Mar 2014 11:46:33 +0000
with message-id
<CAD=6czrvdqkugzcfpykv4c2+056bazkx6wujxuu-cpmhufu...@mail.gmail.com>
and subject line closing 706457
has caused the Debian Bug report #706457,
regarding gnome-shell hangs often when trying to unlock
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
706457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706457
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
version: 3.8.4-5+b1
I'm closing this bug now since it seems to be fixed.
If you can still reproduce it feel free to reopen and provide more info.
thanks
regards
althaser
--- End Message ---
