https://bugs.kde.org/show_bug.cgi?id=494168
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sit...@kde.org
--- Comment #2 from Harald Sitter <sit...@kde.org> ---
My best guess here is that your PAM configuration simply doesn't account for
this.
It's tricky though. The way authentication works is sequentially, i.e. a module
requests authentication and if that fails for whatever reason (or gets
cancelled) the next module in the list gets to try authenticating.
Fundamentally that appears what is happening here. If the fprintd module is
listed first it will request a finger print input, if you don't provide it
within 20-ish seconds the request times out and the regular password module
request authentication kicks in. Hence the delay.
I am not sure we can do much more than have the actual auth request text
displayed in the UI somewhere. Then at least there will be a hint that the
authentication method in question is a finger print rather than a password.
--
You are receiving this mail because:
You are watching all bug changes.
