On Wed, 6 Jul 2022 at 12:26, David Wright <deb...@lionunicorn.co.uk> wrote: > On Wed 06 Jul 2022 at 11:23:00 (+1000), David wrote: > [ … ] > > Then I tried to look for the name of the package that your system > > might be missing ... > > > > $ locate pam_systemd.so > > /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > > > > $ ll /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > > -rw-r--r-- 1 root root 455392 2022-03-21 06:55 > > /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > > > > $ dpkg -S /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > > dpkg-query: no path found matching pattern > > /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > > > > I don't know why that fails. > > $ dpkg -S /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > dpkg-query: no path found matching pattern > /usr/lib/x86_64-linux-gnu/security/pam_systemd.so > $ dpkg -S /lib/x86_64-linux-gnu/security/pam_systemd.so > libpam-systemd:amd64: /lib/x86_64-linux-gnu/security/pam_systemd.so > $ > > It's a consequence of merged /usr, aka usrMerge, where dpkg installs > a file under /lib (the old regime), but the new canonical location is > under /usr/lib (because /lib is now merely a symlink into /usr).
Ahhh yes, I forgot that one :) Cheers