Well,... By chance, I just had it again: # reboot PolicyKit daemon disconnected from the bus. We are no longer a registered authentication agent. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Timeout, server kronecker not responding. So in any case, this isn't fixed with libpam-systemd. Apart from that: - The "openssh-server comes configured _out of the box_ with UsePAM=yes enabled" is just a Debian speciality, the [upstream] default is "no". - There is no reason why people shouldn't be allowed to use UsePAM=no, so even if the pam module would fix this for the =yes case (which it apparently doesn't) we'd still need to cover the =no case. - Since Debian supports diversity wrt init systems I don't see that it would be good to depend on libpam-systemd. - I wouldn't be aware that SSH mandatorily uses dbus (which is I guess the reason that we don't have a dependency on it). Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature