https://bugs.kde.org/show_bug.cgi?id=479964
--- Comment #7 from Colin S <bugs.kde....@zetafleet.com> ---
(In reply to Reuben from comment #6)
> @Nate I addressed that in the second part of my comment.
>
> Smart cards and fingerprinter readers are niche hardware. It's a bug for
> these ugly messages to show in the absence of configuration stating that
> they exist.
Having looked into the source of this problem I don’t see any reasonable way
for KDE to do anything about this. kscreenlocker6 needs PAM to actually load
the correct service so it can query to see if it is available. Instead, PAM
silently falls back to the default service ("other") when the requested service
does not exist. This means when KDE thinks it is checking for
smartcard/fingerprint support, it is actually checking for
"other"-authentication support, because PAM is lying about what service it
loaded. I’m not seeing anything in the PAM API that would allow a caller to
learn that this has happened or to prevent it from happening. So, the
distribution simply needs to include the appropriate PAM service files.
--
You are receiving this mail because:
You are watching all bug changes.
