Package: libpam0g Version: 1.3.1-1 Severity: grave Justification: causes non-serious data loss
Dear Maintainer, after upgrading: libpam-modules (1.1.8-4 => 1.3.1-1) libpam-modules-bin (1.1.8-4 => 1.3.1-1) libpam-runtime (1.1.8-4 => 1.3.1-1) libpam0g (1.1.8-4 => 1.3.1-1) libpam0g-dev (1.1.8-4 => 1.3.1-1) a running xscreensaver instance can no longer authenticate: Feb 13 10:46:22 ripley xscreensaver[977]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Feb 13 10:46:22 ripley xscreensaver[977]: PAM adding faulty module: pam_unix.so Feb 13 10:46:22 ripley xscreensaver[977]: FAILED LOGIN 1 ON DISPLAY ":0.0", FOR "ben" Workaround is using remote access to kill xscreensaver. After a system restart, xscreensaver works normally. In the absence of remote access, a system reset may be required, which may result in the loss of unsaved user data. libpam0g upgrade should test for a running xscreensaver instance and require it to be stopped before upgrade. Kind regards, Ben. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam0g depends on: ii debconf [debconf-2.0] 1.5.70 ii libaudit1 1:2.8.4-2 ii libc6 2.28-7 libpam0g recommends no packages. Versions of packages libpam0g suggests: pn libpam-doc <none> -- debconf information: libpam0g/restart-services: * libraries/restart-without-asking: false libpam0g/xdm-needs-restart: libpam0g/restart-failed:
