Bug 1227074 - kscreenlocker_greet wants to auth with smartcard and fingerprint no matter what
Summary: kscreenlocker_greet wants to auth with smartcard and fingerprint no matter what
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-26 12:21 UTC by Cam Brin
Modified: 2024-06-26 16:03 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cam Brin 2024-06-26 12:21:54 UTC 
I'm on a fresh install done a few days ago. I don't have and never had a smartcard or a fingerprint reader, yet kscreenlocker_greet keeps trying to use them to auth at every login.

It'll output the following upon locking the screen:

Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory
Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or directory
Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so

Then this when unlocking it:

Jun 25 13:59:25 localhost.localdomain unix_chkpwd[3514]: password check failed for user (USERNAME)
Jun 25 13:59:25 localhost.localdomain kscreenlocker_greet[3052]: pam_unix(kde-fingerprint:auth): authentication failure; logname=USERNAME uid=1000 euid=1000 tty= ruser= rhost=  user=USERNAME
Jun 25 13:59:25 localhost.localdomain unix_chkpwd[3515]: password check failed for user (USERNAME)
Jun 25 13:59:25 localhost.localdomain kscreenlocker_greet[3052]: pam_unix(kde-smartcard:auth): authentication failure; logname=USERNAME uid=1000 euid=1000 tty= ruser= rhost=  user=USERNAME

I can login and logout, unlock and lock the screen just fine.
Comment 1 Fabian Vogt 2024-06-26 16:03:09 UTC 
That's the intended behaviour and basically how it has to be with the current PAM design...

Feel free to report that upstream.