Package: systemd Version: 252-2 Severity: normal Dear Maintainer,similar to #749268 there seems to be again the problem, that when logging out, the systemd user process and sd-pam are not killed. Take, e.g., this example: # loginctl kill-session 34 # pgrep -a -u pat 11499 /lib/systemd/systemd --user 11500 (sd-pam) # loginctl list-sessions SESSION UID USER SEAT TTY 13 0 root seat0 tty2 21 0 root seat0 tty2 25 0 root seat0 tty2 33 0 root seat0 tty2 36 0 root seat0 tty2 37 121 sddm seat0 6 sessions listed. So although there is no logind session left, there are still the two user processes around. I added KillUserProcesses=yes but that did not help (is this an additional bug?). Do I miss anything in order to kill the systemd user process automatically?
It looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023545 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024080 might be duplicates.If you think this is a regression in 252 and you can provide a way how this can be reproduced, my advice would be to file this upstream at
https://github.com/systemd/systemd/issues/
OpenPGP_signature
Description: OpenPGP digital signature
