https://bugs.kde.org/show_bug.cgi?id=506567
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #32 from [email protected] --- I can reproduce this on Plasma 6.7.4 without suspending the system. Versions: - kscreenlocker 6.7.4 - fprintd 1.94.5 - libfprint 1.94.100 - Synaptics reader 06cb:00f9 I called the same `kde-fingerprint` PAM service and did not touch the reader. After 30 seconds it returned: ``` Place your finger on the fingerprint reader Verification timed out pam_authenticate: 9 (Authentication service cannot retrieve authentication info) ``` The reader still worked afterwards. `fprintd-list` found one device and both enrolled fingerprints. I did not see USB re-enumeration. In kscreenlocker 6.7.4, `PamWorker::authenticate()` sets `m_unavailable = true` after `PAM_AUTHINFO_UNAVAIL`. Later authentication calls return immediately while that flag is set. This matches the visible behavior: fingerprint unlock works just after locking, then stops after 30 seconds for the rest of that lock session. Adding `timeout=-1` to the `pam_fprintd.so` line avoids the timeout, but this is only a workaround. The retry path is still missing in 6.7.4. -- You are receiving this mail because: You are watching all bug changes.
