fprintd - Problem after resuming from LID closed

Bug #1424368 reported by Alex Botev
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
fprintd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,
So I got this error as I described on the mailing of fprintd:
****
So I have the problem that often after LID open it seems that fprintd does not seem to respond to the PAM module, thus I have about 30 sec of no way of logging in my session, which is a bit frustrating - I get the screen, but no option for finger verification or password. After ~30-40sec I get the password field finally, but note that fprintd has 10 sec timeout in the PAM module. After putting out debug on I got this:

Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Lid closed.
Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Suspending...
Feb 21 10:16:06 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): timeout specified as: 10
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Operation finished.
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Lid opened.
Feb 21 10:16:32 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): get_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Any idea how to fix this or what exactly is the issue?
***
As suggest by Vasily Khoruzhick, I'm posting this here after I recompiled libfprintd and fprintd with debug on for more logging. Also note that I now I use 0.6.0 rather than 0.5.1. The error is still there, but now I have more logs (hope they help someone):

Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Lid closed.
Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Suspending...
Feb 22 00:51:43 botev-ThinkPad-T440 systemd-logind[588]: Removed session c1.
Feb 22 00:51:43 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): Using device /net/reactivated/Fprint/Device/0
Feb 22 10:43:31 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): verify_finger_selected Swipe your finger across the fingerprint reader
Feb 22 10:43:32 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): Verify result: verify-unknown-error
Feb 22 10:43:32 botev-ThinkPad-T440 systemd-logind[588]: Operation finished.
Feb 22 10:43:32 botev-ThinkPad-T440 systemd-logind[588]: Lid opened.
Feb 22 10:43:57 botev-ThinkPad-T440 unity[2193]: pam_fprintd(unity): ReleaseDevice failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Feb 22 10:44:22 botev-ThinkPad-T440 sudo[3507]: pam_fprintd(sudo): Using device /net/reactivated/Fprint/Device/0
Feb 22 10:44:23 botev-ThinkPad-T440 sudo[3507]: pam_fprintd(sudo): verify_finger_selected Swipe your finger across the fingerprint reader
Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): conversation failed
Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): unable to obtain a password
Feb 22 10:45:00 botev-ThinkPad-T440 sudoedit[3507]: pam_unix(sudo:auth): auth could not identify password for [alex]
Feb 22 10:53:48 botev-ThinkPad-T440 gnome-keyring-daemon[1855]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk

Info:
Description: Ubuntu 14.04.2 LTS
Release: 14.04
fprintd and libfprintd - 0.6.0 - compiled from source - http://lists.freedesktop.org/archives/fprint/2015-February/000675.html

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fprintd (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.