Bug#956795: libpam-systemd: fills the logs with messages about pam_systemd.so

[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.

-- 
Francesco Potortì (ricercatore)        Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR          Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa         Skype:  wnlabisti
(gate 20, 1st floor, room C71)         Web:    http://fly.isti.cnr.it


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=C:en_GB:en:en_US:it:fr:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-systemd depends on:
ii  dbus            1.12.16-2
ii  libc6           2.30-4
ii  libpam-runtime  1.3.1-5
ii  libpam0g        1.3.1-5
ii  systemd         245.4-3
ii  systemd-sysv    245.4-3

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information