Created attachment 2188 [details] tgz of /root/drakx Parallel of https://bugzilla.novell.com/show_bug.cgi?id=746594 & https://bugzilla.redhat.com/show_bug.cgi?id=708537 To reproduce: 1-boot with 3 on Grub cmdline 2-login on tty(s) (I did tty2 & tty3, started mc on tty2, did 'init 5' on tty3) 3-'telinit 5' Actual results: 1-KDM appeared on tty1 2-screen cleared to login prompt on tty2 3-screen cleared to login prompt on tty3 Expected results: 1-KDM appeared on tty7 2-mc remained running on uncleared tty2 3-shell prompt remained on uncleared tty3
Keywords: (none) => PATCHCC: (none) => mageiaSource RPM: (none) => systemd
Your expected results are wrong. Should be probably: Expected results: 1-KDM appeared on tty1 2-mc remained running on uncleared tty2 3-shell prompt remained on uncleared tty3 But yes, ttys2 & 3 should be unaffected by this. tty1 will always be nuked due to the conflicts in the prefdm.service.
Upstream patch http://cgit.freedesktop.org/systemd/systemd/commit/?id=4771148bb92ace55eaa6759a53d04a0f2de9b0d2 included in svn.
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to comment #1) > Your expected results are wrong. Should be probably: > Expected results: > 1-KDM appeared on tty1 > 2-mc remained running on uncleared tty2 > 3-shell prompt remained on uncleared tty3 > But yes, ttys2 & 3 should be unaffected by this. tty1 will always be nuked due > to the conflicts in the prefdm.service. In Rawhide last I checked (not for some time), booting into runlevel 3 (which is my preferred init on all test systems, and without plymouth) keeps X on tty[7-10] where it/they belong. tty1 is for text boot messages, and I rarely use it except to view the last screen of boot messages (except in installations that clear it by default and I can't figure out how to prevent the clearing, such as in Mandriva/Mageia). In openSUSE I still make use of the option to not use systemd except on a very few systems purely used for testing systemd in Factory. So here at least, there should rarely if ever be a reason to nuke tty1.
I even linked to the commit message where this is clearly explained that tty1 is still nuked due to the conflict in prefdm.service. If you want you can copy the prefdm.service unit to /etc/systemd/system and customise it to taste such that it does not conflict with getty@tty1. So your comments about how it works in Rawhide are wrong. This is an old discussion that was had on the mailing list a long time ago. RC stage is NOT the time to revisit this, so no further comments on this topic please. If you strongly disagree, please participate in discussion when planning mga3.