http://bugzilla.opensuse.org/show_bug.cgi?id=968727
http://bugzilla.opensuse.org/show_bug.cgi?id=968727#c29
patrick shanahan
(In reply to patrick shanahan from comment #27)
(In reply to Dr. Werner Fink from comment #26)
(In reply to patrick shanahan from comment #25) How this? AFAICS from my tests the fixed 228 does *not* close the tty's
then it hasn't been published: systemd-228-2.1.x86_64 closes tty's on all five of my local boxes.
Well it's going to take some time before the fix reaches Tumbleweed...
So now I'm not sure which version of systemd you were using from the beginning of your testing.
systemd-228-2.1.x86_64
This repo should contain the fixes:
http://download.opensuse.org/repositories/Base:/System/openSUSE_Tumbleweed/
Can you redo your test with systemd updated from it ?
yes
Specially the test which consists of mounting your USB drive from runlevel3 and do the switch to runlevel5. According to one of your previous comment your drive isn't mounted anymore.
Before doing this test, change the log level of systemd to "debug" with: $ systemd-analyze set-log-level debug
then after your test restore the previous log level to the default "info" and the the content of the journal.
runlevel 5, systemd-228-10.2, external usb sdb mounted at: /run/media/paka/TOSHIBA EXT /var/run/media/paka/TOSHIBA EXT (Don't know why it mounts two places) switch to runlevel 3 tty6 previously open is dropped, relogged on /dev/sdb is no longer mounted mounted /dev/sdb to /mnt/external/ systemctl isolate graphical.target tty6 remained open mount /mnt/external persisted systemctl isolate multi-user tty6 remained open mount /mnt/external persisted systemctl isolate graphical umount /mnt/external used "Device Notifier" applet to mount /dev/sdb2 mounted to 2 locations: /run/media/paka/TO.. /var/run/media/paka/TO.. systemctl isolate multi-user tty6 remained open /dev/sdb2 is no longer mounted journalctl --since "2016-03-03 12:00" > journal.logs.txt http://wahoo.no-ip.org/~paka/journal.logs.txt -- You are receiving this mail because: You are on the CC list for the bug.