Michael Biebl <bi...@debian.org> writes: > Actually in Debian, su *does* start a logind session. If you look at > > /etc/pam.d/su it includes /etc/pam.d/common-session
It does: # The standard Unix authentication modules, used with # NIS (man nsswitch) as well as normal /etc/passwd and # /etc/shadow entries. @include common-auth @include common-account @include common-session > If libpam-systemd is installed, there will be an entry in common-session > like this: > session optional pam_systemd.so libpam-systemd is installed and common-session includes this line (and it hasn't been modified in any way): # and here are more per-package modules (the "Additional" block) session required pam_unix.so session optional pam_systemd.so # end of pam-auth-update config > If libpam-systemd is installed and enabled, that should actually work. No, it does not work. This is Debian stable/Jessie with all the latest updates installed. I have three identical machines setup like this and on all three it does not work. > It's unclear to me, why you filed this as an issue against systemd? It looked to me like a problem in systemd/libpam-systemd. Do you still believe I should file it against su (and runuser, and maybe sudo for good measure)?
