My system thankfully does not use the systemd and the sddm was compiled accordingly with "consolekit pam -elogind -systemd -test". However, I keep getting the following error messages in the system log:
Oct 30 11:08:02 hooverix sddm-helper: PAM unable to dlopen(/lib64/security/pam_systemd.so): /lib64/security/pam_systemd.so: cannot open shared object file: No such file or directory
Oct 30 11:08:02 hooverix sddm-helper: PAM adding faulty module: /lib64/security/pam_systemd.so
Oct 30 11:08:02 hooverix sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
The sddm appears to work despite this but as this problem is pam-related, I am concerned if the security is not compromised because sddm is perhaps confused about the system it runs on and the pam modules it should use.
sddm installs sddm-greeter.pam which contains:
session optional @LOGIND_PAM_MODULE@
where @LOGIND_PAM_MODULE@ is configured by:
This shouldn't affect anything if neither systemd nor logind are being used, but it would be nice to fix upstream removing this bogus line if neither session tracker is being used.