Bug 67267

Summary:	>=systemd-205 causes shell unlock to fail sometimes
Product:	systemd	Reporter:	Pacho Ramos <pachoramos1>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED DUPLICATE	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium	CC:	alexander, freedesktop, gnome, markpariente
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Pacho Ramos 2013-07-24 17:43:40 UTC

As reported downstream:
https://bugs.gentoo.org/show_bug.cgi?id=477954

From time to time, I am unable to unlock screen from gnome-shell locker, I see a yellow "Authentication error" message below password box, messages like the following are recorded in journalctl:
Jul 23 16:53:24 siegeengine systemd-logind[541]: Removed session c1.
Jul 23 16:53:24 siegeengine systemd[1]: Stopped User Manager for 107.
Jul 23 16:53:24 siegeengine systemd[1]: Stopping user-107.slice.
Jul 23 16:53:24 siegeengine systemd[1]: Removed slice user-107.slice.
Jul 23 16:53:51 siegeengine /etc/gdm/Xsession[947]: Window manager warning: Log level 16: value "-8.000000" of type `gfloat' is invalid or out of range for property `width' of type `gfloat'
Jul 23 16:53:51 siegeengine /etc/gdm/Xsession[947]: Window manager warning: Log level 16: value "-8.000000" of type `gfloat' is invalid or out of range for property `height' of type `gfloat'
Jul 23 16:53:53 siegeengine /etc/gdm/Xsession[947]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600052 (New Tab - )
Jul 23 16:53:53 siegeengine /etc/gdm/Xsession[947]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Jul 23 16:54:53 siegeengine gdm[561]: GdmManager: could not fetch uid of session 'c1': No such file or directory
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!   Failed to open reauthentication channel
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     message = '"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No sessions for mark available for reauthentication"'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/gdm/util.js"'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     lineNumber = '254'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     stack = '"0 anonymous("result" = [object GObject_Object], "client" = [object GObject_Object])@/usr/share/gnome-shell/js/gdm/util.js:254
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: 1 wrapper([object GObject_Object], [object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: "'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!   Exception was: TypeError: this._userVerifier is undefined
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     message = '"this._userVerifier is undefined"'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/gdm/util.js"'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     lineNumber = '436'
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: JS ERROR: !!!     stack = '"(false)@/usr/share/gnome-shell/js/gdm/util.js:436
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: wrapper(false)@/usr/share/gjs-1.0/lang.js:213
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: ("Failed to open reauthentication channel",[object GLib_Error])@/usr/share/gnome-shell/js/gdm/util.js:249
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: wrapper("Failed to open reauthentication channel",[object GLib_Error])@/usr/share/gjs-1.0/lang.js:213
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: ([object GObject_Object],[object GObject_Object])@/usr/share/gnome-shell/js/gdm/util.js:265
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: wrapper([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
Jul 23 16:54:53 siegeengine /etc/gdm/Xsession[947]: "'

This looks to be a regression introduced in 205

Thanks!

Comment 1 Lennart Poettering 2013-07-26 01:49:17 UTC

Could you recheck this with 206 please?

Comment 2 Lennart Poettering 2013-07-26 01:53:27 UTC

Or actually, let's turn this around, I am pretty sure this is fixed with a full yupgraded 206. Will close the bug now. If you manage to reproduce the issue with a fully updated 206, feel free to reopen. Thanks.

Comment 3 Mark Pariente 2013-07-26 02:09:42 UTC

Actually the logs that Pacho posted are with systemd-206, so no this is not fixed at 206.

Comment 4 Albert Hopkins 2013-07-26 10:01:03 UTC

(In reply to comment #3)
> Actually the logs that Pacho posted are with systemd-206, so no this is not
> fixed at 206.

Correct.  I (also) experienced this issue going from 204 straight to 206.

Comment 5 Alexandre Rostovtsev 2013-07-29 02:10:19 UTC

I believe this is a duplicate of bug #67273.

I was experiencing these symptoms with systemd-206, and applying cba38758b4d49c6fe7c2f0eea255e11ee9df23eb fixed it for me.

Comment 6 Lennart Poettering 2013-07-29 14:43:42 UTC


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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.