Control: reassign -1 libpam0g Am 15.04.20 um 12:39 schrieb Francesco Potortì: > Package: libpam-systemd > Version: 245.4-3 > Severity: minor > > I use a testing distribution that I update daily. On 12 April I started > seeing these message in auth.log: > > Apr 15 03:55:01 tucano CRON[3019529]: PAM adding faulty module: pam_systemd.so > Apr 15 03:55:01 tucano CRON[3019530]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:55:01 tucano CRON[3019530]: PAM adding faulty module: pam_systemd.so > Apr 15 03:56:01 tucano CRON[3019721]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:56:01 tucano CRON[3019721]: PAM adding faulty module: pam_systemd.so > Apr 15 03:56:01 tucano CRON[3019722]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:56:01 tucano CRON[3019722]: PAM adding faulty module: pam_systemd.so > Apr 15 03:57:01 tucano CRON[3019911]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:57:01 tucano CRON[3019911]: PAM adding faulty module: pam_systemd.so > Apr 15 03:57:01 tucano CRON[3019910]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:57:01 tucano CRON[3019910]: PAM adding faulty module: pam_systemd.so > Apr 15 03:58:01 tucano CRON[3020088]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:58:01 tucano CRON[3020088]: PAM adding faulty module: pam_systemd.so > Apr 15 03:58:01 tucano CRON[3020089]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot open shared object file: No such file or > directory > Apr 15 03:58:01 tucano CRON[3020089]: PAM adding faulty module: pam_systemd.so > Apr 15 03:59:01 tucano CRON[3020273]: PAM unable to dlopen(pam_systemd.so): > /lib/security/pam_systemd.so: cannot op > > I observe: > > $ apt-file find pam_systemd.so > libpam-systemd: /lib/x86_64-linux-gnu/security/pam_systemd.so > > $ locate pam_systemd.so > /lib/x86_64-linux-gnu/security/pam_systemd.so > > And apparently no problems (I can login via ssh), that's why I marked > the bug as minor. >
I'm reassigning this to libpam0g. It should load the module from the multi-arch path. I'm not sure why it tries to load it from /lib/security. This doesn't look like a libpam-systemd error to me, as the error happens even before the module is loaded.
signature.asc
Description: OpenPGP digital signature
