Summary: | gnome-base/gnome-shell-3.8* session unlock broken with >systemd-204 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark R. Pariente <markpariente> |
Component: | [OLD] GNOME | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, dominik.kriegner, gentoo-bugs, gnome, marduk, me, ooblick, publiosulpicio |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=67267 | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=67273 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 463242 |
Description
Mark R. Pariente
2013-07-24 00:08:16 UTC
I see this problem from time to time (can be workarounded clicking on "Cancel" and retrying some number of times when it occurs). CCing systemd people (as a side note: using -O3 with gcc4 is not recommended at all http://www.gentoo.org/doc/en/gcc-optimization.xml ) I can reliably work around this by switching to another vt (when the 'curtain' is down), and then back. (In reply to Pacho Ramos from comment #2) > (as a side note: using -O3 with gcc4 is not recommended at all > http://www.gentoo.org/doc/en/gcc-optimization.xml ) Thanks for the suggestion - I've always (since 2004) used system wide -O3 without any negative consequences. I have plenty of memory and disk space to spare, and stuff runs quite well in terms of speed. If anything I prefer to keep using it so there's someone out there testing -O3 with all kinds of packages and report bugs to gcc or the affected package if anything blows up :) For me, it fails every time :) I have also hit this bug. In my case, this was because I had the fprint USE-flag enabled, and guess what: # cat /etc/pam.d/gdm-fingerprint account include system-login auth substack fingerprint-auth auth optional pam_gnome_keyring.so password required pam_deny.so session substack system-login session optional pam_gnome_keyring.so auto_start And the /etc/pam.d/fingerprint-auth file does not exist on a fresh install. Created it, fixed the problem: # cat /etc/pam.d/fingerprint-auth auth required pam_fprintd.so For me (hitting this failure every time with systemd-206, gdm[-fprintd]), journalctl shows the following: Jul 28 21:32:24 rook gdm[10417]: GdmManager: could not fetch uid of session 'c2': No such file or directory Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! Failed to open reauthentication channel Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! message = '"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No sessions for tetromino available fo Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/gdm/util.js"' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! lineNumber = '254' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! stack = '"0 anonymous("result" = [object GObject_Object], "client" = [object GObject_Object])@/usr/shar Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: 1 wrapper([object GObject_Object], [object GObject_Object])@/usr/share/gjs-1.0/lang.js:213 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: "' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! Exception was: TypeError: this._userVerifier is undefined Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! message = '"this._userVerifier is undefined"' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/gdm/util.js"' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! lineNumber = '436' Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: JS ERROR: !!! stack = '"(false)@/usr/share/gnome-shell/js/gdm/util.js:436 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: wrapper(false)@/usr/share/gjs-1.0/lang.js:213 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: ("Failed to open reauthentication channel",[object GLib_Error])@/usr/share/gnome-shell/js/gdm/util.js:249 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: wrapper("Failed to open reauthentication channel",[object GLib_Error])@/usr/share/gjs-1.0/lang.js:213 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: ([object GObject_Object],[object GObject_Object])@/usr/share/gnome-shell/js/gdm/util.js:265 Jul 28 21:32:24 rook /etc/gdm/Xsession[10532]: wrapper([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/lang.js:213 This was fixed in systemd git master by this patch: http://cgit.freedesktop.org/systemd/systemd/commit/?id=cba38758b4d49c6fe7c2f0eea255e11ee9df23eb Applying it and rebooting allows me to unlock gnome-shell. (In reply to Alexandre Rostovtsev from comment #8) > This was fixed in systemd git master by this patch: > http://cgit.freedesktop.org/systemd/systemd/commit/ > ?id=cba38758b4d49c6fe7c2f0eea255e11ee9df23eb > > Applying it and rebooting allows me to unlock gnome-shell. Same... (even seems to work w/o rebooting). *** Bug 479084 has been marked as a duplicate of this bug. *** In 206-r1 that I just committed. |