You are not logged in.
I was surprised to see this after running 'journalctl -p 3 -xb' just now:
Oct 13 08:47:10 arch sddm-helper[670]: PAM unable to dlopen(/usr/lib/security/pan_faildelay.so): /usr/lib/security/pan_faildelay.so: cannot open shared object file: No such file or directory
Oct 13 08:47:10 arch sddm-helper[670]: PAM adding faulty module: /usr/lib/security/pan_faildelay.so
So I've searched around the forums (Arch and sddm) and nothing seems to be coming up. It's not causing any issues as far as I'm aware. It just seems to be a typo (pan instead of pam). Should this be reported as a bug? And, if so, with whom?
Thanks!
Last edited by rs410ga (2019-10-13 16:00:32)
Offline
My package's name is correct:
pacman -Fsx .*faildelay.*
core/pam 1.3.1-1
usr/lib/security/pam_faildelay.so
usr/share/doc/Linux-PAM/sag-pam_faildelay.html
usr/share/man/man8/pam_faildelay.8.gz
multilib/lib32-pam 1.3.1-1
usr/lib32/security/pam_faildelay.soso this seems to be an anomaly on your system, for whatever reason that you will want to identify.
Offline
If it's really trying to dlopen pan_faildelay.so, that's something that should be reported upstream.
Edit: grep through /etc/pam.d/ first, it could be a misconfiguration.
Last edited by Scimmia (2019-10-13 15:45:08)
Offline
If it's really trying to dlopen pan_faildelay.so, that's something that should be reported upstream.
Edit: grep through /etc/pam.d/ first, it could be a misconfiguration.
You're exactly correct though I'm not sure where the misconfiguration came from.
Thanks.
Offline
Use pacman -Qo on whatever file you found the typo in. If it came from a package, it should be checked out further.
Offline
Use pacman -Qo on whatever file you found the typo in. If it came from a package, it should be checked out further.
pambase
I feel confident that I haven't touched that file since I installed the system but this is the first time I've seen it in the logs. Nonetheless, I'm marking it up to fat fingering on my part.
Thanks
Offline