GNOME Bugzilla – Bug 709607
lock-screen unlocks computer after several tries
Last modified: 2019-02-24 16:09:29 UTC
Hi, In F20, it happens quite often, that screen is not unlocked on first attempt. The spinner just keeps spinning but nothing happens. I am using SSSD, not sure if it might be related. This is snippet of my journalctl output: říj 08 07:46:45 unused-4-115.brq.redhat.com gnome-session[1641]: (gnome-settings-daemon:1826): power-plugin-WARNING **: failed to turn the kbd backlight off: GDBus.Error:org.freedesktop říj 08 07:46:45 unused-4-115.brq.redhat.com fprintd[20734]: Launching FprintObject říj 08 07:46:45 unused-4-115.brq.redhat.com fprintd[20734]: ** Message: D-Bus service launched with name: net.reactivated.Fprint říj 08 07:46:45 unused-4-115.brq.redhat.com fprintd[20734]: ** Message: entering main loop říj 08 07:46:51 unused-4-115.brq.redhat.com gdm-password][20739]: pam_unix(gdm-password:auth): conversation failed říj 08 07:46:51 unused-4-115.brq.redhat.com gdm-password][20739]: pam_unix(gdm-password:auth): auth could not identify password for [vondruch] říj 08 07:46:56 unused-4-115.brq.redhat.com gdm-password][20739]: pam_sss(gdm-password:auth): authentication failure; logname=vondruch uid=0 euid=0 tty=:0 ruser= rhost= user=vondruch říj 08 07:46:56 unused-4-115.brq.redhat.com gdm-password][20739]: [81B blob data] říj 08 07:46:56 unused-4-115.brq.redhat.com gdm-password][20739]: gkr-pam: no password is available for user říj 08 07:46:58 unused-4-115.brq.redhat.com fprintd[20734]: ** Message: No devices in use, exit říj 08 07:47:07 unused-4-115.brq.redhat.com gdm-password][20754]: pam_unix(gdm-password:auth): conversation failed říj 08 07:47:07 unused-4-115.brq.redhat.com gdm-password][20754]: pam_unix(gdm-password:auth): auth could not identify password for [vondruch] říj 08 07:47:07 unused-4-115.brq.redhat.com dbus-daemon[772]: dbus[772]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' říj 08 07:47:07 unused-4-115.brq.redhat.com dbus[772]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' říj 08 07:47:07 unused-4-115.brq.redhat.com systemd[1]: Starting Fingerprint Authentication Daemon... říj 08 07:47:07 unused-4-115.brq.redhat.com dbus-daemon[772]: dbus[772]: [system] Successfully activated service 'net.reactivated.Fprint' říj 08 07:47:07 unused-4-115.brq.redhat.com dbus[772]: [system] Successfully activated service 'net.reactivated.Fprint' říj 08 07:47:07 unused-4-115.brq.redhat.com systemd[1]: Started Fingerprint Authentication Daemon. říj 08 07:47:07 unused-4-115.brq.redhat.com fprintd[20763]: Launching FprintObject říj 08 07:47:07 unused-4-115.brq.redhat.com fprintd[20763]: ** Message: D-Bus service launched with name: net.reactivated.Fprint říj 08 07:47:07 unused-4-115.brq.redhat.com fprintd[20763]: ** Message: entering main loop říj 08 07:47:08 unused-4-115.brq.redhat.com gdm-password][20754]: pam_sss(gdm-password:auth): authentication failure; logname=vondruch uid=0 euid=0 tty=:0 ruser= rhost= user=vondruch říj 08 07:47:08 unused-4-115.brq.redhat.com gdm-password][20754]: [81B blob data] říj 08 07:47:08 unused-4-115.brq.redhat.com gdm-password][20754]: gkr-pam: no password is available for user říj 08 07:47:12 unused-4-115.brq.redhat.com unix_chkpwd[20777]: password check failed for user (vondruch) říj 08 07:47:12 unused-4-115.brq.redhat.com gdm-password][20771]: pam_unix(gdm-password:auth): authentication failure; logname=vondruch uid=0 euid=0 tty=:0 ruser= rhost= user=vondruch říj 08 07:47:14 unused-4-115.brq.redhat.com gdm-password][20771]: pam_sss(gdm-password:auth): authentication success; logname=vondruch uid=0 euid=0 tty=:0 ruser= rhost= user=vondruch říj 08 07:47:14 unused-4-115.brq.redhat.com gdm-password][20771]: gkr-pam: unlocked login keyring říj 08 07:47:38 unused-4-115.brq.redhat.com fprintd[20763]: ** Message: No devices in use, exit Thanks
Created attachment 256891 [details] /var/log/secure This is the relevatn part of /var/log/secure
This might be an SSSD issue. I asked Vit to raise the debug_level of SSSD so that we get some more information about what's happening.
It happened again, but the additional logging does not unveil any new information :/
I will be away until Tuesday evening, but feel free to send me the SSSD logs. You can send them privately to avoid leaking any personal info into the bugzilla.
I have the same issue from time to time, usually when system is under heavy load, but I don't have sssd
Do you still experience that problem with newer versions?
*** Bug 733612 has been marked as a duplicate of this bug. ***
I have not observed the issue on my F20 recently.
OK, closing this bug as obsolete then. Please reopen if you see the problem again.
I still hit this with 3.12 (exactly the same symptoms as reported in bug 733612) but, as I commented in comment #6, looks to occur more frequently with more load
Reopening as per comment 10.
(In reply to Pacho Ramos from comment #10) > I still hit this with 3.12 Is this still a problem in gnome-shell 3.24 or 3.22?
(In reply to André Klapper from comment #12) > Is this still a problem in gnome-shell 3.24 or 3.22? Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment and if the problem still happens in 3.30 or later. Thanks!