Simply manually making pam_systemd.so a symlink to pam_elogind.so gets this working.
For what it’s worth.
I have no idea if making such a symlink as part of the install script if pam_systemd.so isn’t present is permitted by Debian “POLICY”, however, it works....
Even if it would mask similar cases where things only look for the system variant.
Given the tests coded in:
liblightdm-gobject/power.c
using org.freedesktop.login1 testing for each of Suspend, Hibernate, Restart and Shutdown
are failing & shouldn’t regardless if libpam_systemd or libpam-elogind is in use, it’s possible this bug is
a problem in policykit-1 which has been somewhat heavily hacked at to provide support for both
without having to compile different versions against different libraries.
It might be worth a conversation with the maintainers of said package to determine exactly who’s bug
this actually is.
I vaguely seem to recall that when I compiled policykit-1 v 0.115 (what experimental had at the time)
Against libelogind-dev rather than libsystemd-dev on a system using sysvinit-core and openrc and
also using the patch referenced here:
https://gitlab.freedesktop.org/polkit/polkit/issues/29
Then this issue went away. My memory may be playing me tricks however.
Even though I didn’t do it properly & just used an equivs package & a symlink from libelogind.pc
to libsystemd.pc in order to fool the build-deps & actually build the packages.
I’m afraid that doing the job properly or determining exactly what’s going on here is slightly above
my skill level. Frankly I wish I could tell & provide a patch for whichever package is at fault.