Your message dated Mon, 12 Apr 2021 13:20:04 +0200 with message-id <20210412112004.u7di2wo5orktpvao@flashgordon> and subject line rebooting helps has caused the Debian Bug report #986759, regarding libpam-otpw: pam_otpw.so is installed in /lib/security/, but should be in /lib/x86_64-linux-gnu/security/ to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libpam-otpw Version: 1.5-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: a...@debian.org Dear Maintainer, after trying to set up libpam-otpw on bullseye, it did not work and the line: PAM unable to dlopen(pam_otpw.so): /lib/x86_64-linux-gnu/security/pam_otpw.so: cannot open shared object file: No such file or directory showed up in the journal. Copying pam_otpw.so from /lib/security/pam_otpw.so to /lib/x86_64-linux-gnu/security/ fixed the problem. It looks like pam_otpw.so is installed in an outdated location. Thanks and best regards, Andi
--- End Message ---
--- Begin Message ---Hi, after a bit more investigation, I found that the issue I saw is probably related to multiarch. After a reboot, /lib/security/pam_otpw.so is found and everything works fine. Therefore I close the bug. Sorry for the noise and best regards, Andi
--- End Message ---
