Comment 28 for bug 1309535

I can confirm the problem with `journalctl`:

Jan 03 01:05:13 tron lightdm[12730]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or dire
Jan 03 01:05:13 tron lightdm[12730]: PAM adding faulty module: pam_kwallet.so
Jan 03 01:05:13 tron lightdm[12730]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or di
Jan 03 01:05:13 tron lightdm[12730]: PAM adding faulty module: pam_kwallet5.so
Jan 03 01:05:14 tron lightdm[12841]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or dire
Jan 03 01:05:14 tron lightdm[12841]: PAM adding faulty module: pam_kwallet.so
Jan 03 01:05:14 tron lightdm[12841]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or di
Jan 03 01:05:14 tron lightdm[12841]: PAM adding faulty module: pam_kwallet5.so

The lines were created during logins, i.e. initial logins or after locking the screen (xflock4) and unlocking it again.

The workaround I used was to change /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter and comment out (#) the following lines (in both files):

#auth optional pam_kwallet.so
#auth optional pam_kwallet5.so
...
#session optional pam_kwallet.so auto_start
#session optional pam_kwallet5.so auto_start

So far the systemd log is clear of those loglines. A different workaround would be to simply install the KDE component.