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 733612 - non-unlocking lockscreen
non-unlocking lockscreen
Status: RESOLVED DUPLICATE of bug 709607
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: 2014-07-23 16:44 UTC by Matěj Cepl
Modified: 2014-11-09 20:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matěj Cepl 2014-07-23 16:44:21 UTC
I usually leave my computer running throughout the night. When I come to it in the morning most of the time I cannot unlock on the first try. When I enter password, the lockscreen starts to unlock but it never finishes. I have to cancel unlocking (via [Esc]) and then to try again, which works perfectly and then I am in. This is what I have in the journalctl

Jun 23 06:57:08 wycliff dbus-daemon[1370]: dbus[1370]: [system]
Activating via systemd: service name='net.reactivated.Fprint'
unit='fprintd.service'
Jun 23 06:57:08 wycliff dbus[1370]: [system] Activating via systemd:
service name='net.reactivated.Fprint' unit='fprintd.service'
Jun 23 06:57:08 wycliff systemd[1]: Starting Fingerprint Authentication
Daemon...
Jun 23 06:57:09 wycliff dbus-daemon[1370]: dbus[1370]: [system]
Successfully activated service 'net.reactivated.Fprint'
Jun 23 06:57:09 wycliff dbus[1370]: [system] Successfully activated
service 'net.reactivated.Fprint'
Jun 23 06:57:09 wycliff systemd[1]: Started Fingerprint Authentication
Daemon.
Jun 23 06:57:09 wycliff fprintd[16876]: Launching FprintObject
Jun 23 06:57:09 wycliff fprintd[16876]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint
Jun 23 06:57:09 wycliff fprintd[16876]: ** Message: entering main loop
Jun 23 06:57:22 wycliff gdm-password][16881]:
pam_unix(gdm-password:auth): conversation failed
Jun 23 06:57:22 wycliff gdm-password][16881]:
pam_unix(gdm-password:auth): auth could not identify password for [matej]
Jun 23 06:57:22 wycliff gdm-password][16881]: gkr-pam: no password is
available for user
Jun 23 06:57:39 wycliff fprintd[16876]: ** Message: No devices in use, exit

Any ideas?
Comment 1 Bastien Nocera 2014-11-09 20:33:04 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.

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