Package: libpam-script Version: 1.1.9-4+b1 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: c2h...@web.de
Dear Maintainer, after reinstalling my (FAI-driven) installation with bullseye (using stretch before and ignoring buster), I found that pam-script doesn't work anymore. /var/log/auth.log claims that: PAM unable to dlopen(pam_script.so): /lib/x86_64-linux-gnu/security/pam_script.so: Couldn't open Shared-Object-file: File or directory not found PAM adding faulty module: pam_script.so Your package contains the file, but it lives in a wrong directory (and for me there is no other file in there): /lib/security/pam_script.so all other pam_*.so files live in /lib/x86_64-linux-gnu/security/ and a simple ln -s /lib/security/pam_script.so /lib/x86_64-linux-gnu/security/pam_script.so made pam_script work again. I'm not knowing the details of PAM and pam_script, but I think simply moving the directory should be the right solution. Please fix it in the remaining bullseye-freeze. Thank you Christian Meyer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-script depends on: ii libc6 2.31-9 ii libpam0g 1.4.0-4 libpam-script recommends no packages. libpam-script suggests no packages. -- no debconf information
