Observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0Double checked that
etc/systemd/system/getty.target.wants/getty@tty1.service as well as
/lib/systemd/system/getty@.service both contain 'IgnoreOnIsolate=yes' One user
in above forum reported the same for Fedora since Fedora21, so not debian
specific (some wild guesses were that its rather introduced by xserver setuid
change than by systemd itself?).Michael Singer reported in IRC that he had no
problems on Nov 12 and observed the bug on Nov 15, probably systemd 227-2 ->
227-3----New test with several ttys, 3x root on tty1,tty2,tty3, user on tty4.
On isolate-command, all of them get logged out.## System running inside
Virtualbox 5.0.8.10linux-image-4.3.0-towo.3-siduction-686 4.3-2 systemd
228-1plasma-desktop 4:5.4.2-1kde-runtime 4:15.08.2-1xserver-xorg-core
2:1.17.3-2Before isolate command, root on tty1, user-session active:#loginctl
list-sessionsSESSION UID USER SEATc1
105 lightdm seat01 1000 myuser
seat02 0 root seat03
sessions listedAfter isolate command, root on tty1 re-logged in:#loginctl
list-sessionsSESSION UID USER
SEATq3 0 root seat01
sessions listedPart of journal between the two root logins (before/after
isolate command) added.
