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 695048 - lock screen authentication failure
lock screen authentication failure
Status: RESOLVED DUPLICATE of bug 684172
Product: gnome-shell
Classification: Core
Component: lock-screen
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-03-03 07:08 UTC by darkxst
Modified: 2013-03-03 20:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description darkxst 2013-03-03 07:08:35 UTC 
Occasionally when trying to unlock computer, the lock screen will fail with "authentication failed" message, before you start to enter password.

    JS ERROR: !!!   Failed to open reauthentication channel
    JS ERROR: !!!     message = '"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Unable to find appropriate session for user darkxst"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/gdm/util.js"'
    JS ERROR: !!!     lineNumber = '188'
    JS ERROR: !!!     stack = '"0 anonymous()@/usr/share/gnome-shell/js/gdm/util.js:188
1 wrapper()@/usr/share/gjs-1.0/lang.js:213

Once this happens it become stuck and must restart gnome-shell to be able to try again.
Comment 1 Giovanni Campagna 2013-03-03 13:03:29 UTC 
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.

(Disregard the last comments in the linked bug, they're related to a different issue. And please check the output of loginctl, it should be similar to comment #15)

*** This bug has been marked as a duplicate of bug 684172 ***
Comment 2 darkxst 2013-03-03 20:17:46 UTC 
This is happening on ConsoleKit, I am not sure how to get the equivalent output from this.