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 699806 - unable to unlock gnome in ThinLinc (VNC)
unable to unlock gnome in ThinLinc (VNC)
Status: RESOLVED DUPLICATE of bug 726283
Product: gnome-shell
Classification: Core
Component: lock-screen
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-07 09:10 UTC by Pierre Ossman
Modified: 2014-04-11 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pierre Ossman 2013-05-07 09:10:44 UTC
(originally reported against Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=960149)

Trying to unlock Gnome in a remote ThinLinc session results in "Authentication error" and a never ending spinner. This is what the log has to say:

    JS ERROR: !!!   Failed to open reauthentication channel
    JS ERROR: !!!     message = '"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gdm_5fdisplay_5ferror.Code2: Error getting seat id from systemd: No such file or directory"'
    JS ERROR: !!!     fileName = 'undefined'
    JS ERROR: !!!     lineNumber = 'undefined'
    JS ERROR: !!!     stack = 'undefined'
    JS ERROR: !!!   Exception was: TypeError: this._userVerifier is undefined
    JS ERROR: !!!     message = '"this._userVerifier is undefined"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/gdm/util.js"'
    JS ERROR: !!!     lineNumber = '456'
    JS ERROR: !!!     stack = '"(false)@/usr/share/gnome-shell/js/gdm/util.js:456
wrapper(false)@/usr/share/gjs-1.0/lang.js:213
("Failed to open reauthentication channel",[object GObject_Boxed])@/usr/share/gnome-shell/js/gdm/util.js:250
wrapper("Failed to open reauthentication channel",[object GObject_Boxed])@/usr/share/gjs-1.0/lang.js:213
([object GObject_Object],[object GObject_Object])@/usr/share/gnome-shell/js/gdm/util.js:266
wrapper([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
"'

Since this is a remote session, a lack of a seat is perfectly normal.

Similar behaviour has been noticed on Fedora 18, but the log there is more unclear:

    JS ERROR: !!!   Exception was: TypeError: Object 0x7fee89e73e18 is not a subclass of (null), it's a GLib_Error
    JS ERROR: !!!     message = '"Object 0x7fee89e73e18 is not a subclass of (null), it's a GLib_Error"'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/gdm/util.js"'
    JS ERROR: !!!     lineNumber = '159'
    JS ERROR: !!!     stack = '"([object _private_Gdm_Client],[object _private_Gio_SimpleAsyncResult])@/usr/share/gnome-shell/js/gdm/util.js:159
wrapper([object _private_Gdm_Client],[object _private_Gio_SimpleAsyncResult])@/usr/share/gjs-1.0/lang.js:204
"'


If the lock screen relies on GDM for PAM access, it really shouldn't start at all if it isn't launched from GDM.
Comment 1 Giovanni Campagna 2013-05-07 09:37:01 UTC
I'm not sure I understand this setup.

Gdm seems to be there (we check its presence at startup, and the DBus error comes from gdm), so who is running gnome-shell and where?
Comment 2 Pierre Ossman 2013-05-07 10:38:14 UTC
Gnome-shell is running in a VNC server, not in the local X server controlled by gdm. Hence the lack of seat and access to gdm. It does however have a full session in other regards, like a PAM session, systemd session, etc.
Comment 3 Aaron Lu 2013-07-16 02:39:12 UTC
I have the same problem when upgraded to Fedora 19, which comes with gnome 3.8 with no fallback mode. So I've been using gnome-shell in vnc session too now, and once the screen is locked, unlock is impossible with the "authentication failed" error message.
Comment 4 Ray Strode [halfline] 2014-04-11 12:35:05 UTC
i fixed this in GDM a while back

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