[Bug 768788] New: [systemd][3 on cmdline] X session tty locations not predictable (:1 not always on tty8; :0 not always on tty7)
https://bugzilla.novell.com/show_bug.cgi?id=768788 https://bugzilla.novell.com/show_bug.cgi?id=768788#c0 Summary: [systemd][3 on cmdline] X session tty locations not predictable (:1 not always on tty8; :0 not always on tty7) Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa-bugs@suse.de CC: fcrozat@suse.com Found By: --- Blocker: --- Not new in 12.2B2. I don't remember how far back this began, but possibly when systemd first appeared in ~12.1M3 last summer. Neither splashy nor bootsplash are installed on any of my systems. All my Grub stanzas include splash=verbose on cmdline. AFAICT, plymouth though installed never appears to run, which is my strong preference. To reproduce [i945G host gx62b]: 1-boot (with 3 on cmdline) 2-login on tty2 3-login on tty3 4-login on tty4 5-# init 5 on tty3 6-login in KDM3 7-$ startx -- :1 on tty4 Actual results: 1-KDM is on tty7 2-:1 X session is on tty5 Expected results: 1-KDM is on tty7 2-:1 X session is on tty8 Alternate reproduce [rv380 host big31]: 1-boot (with 3 on cmdline) 2-login on tty3 3-# startx Actual results: 1-KDE4 session is on tty2 2-login prompts on tty1, tty2, tty4, tty5, tty6, tty7, tty8, tty9 after KDE4 exited Expected results: 1-KDE4 session is on tty7 2-login prompts only on tty1, tty2, tty4, tty5, tty6 after KDE4 exited Alternate 2 reproduce [rv380 host big31]: 1-boot (with 3 on cmdline) 2-login on tty2 3-login on tty3 4-login on tty4 5-# startx on tty3 6-$ startx -- :1 on tty4 Actual results: 1-root's KDE4 is on tty6 2-:1 X session is on tty7 3-no login prompt on tty6 after KDE exited Expected results: 1-root's KDE4 is on tty7 2-:1 X session is on tty8 3-login prompt on tty6 after KDE exited Note: I don't expect this to matter, as I've not tested stock, but noting in case it might. I have /lib/systemd/system/getty@tty1.service as a symlink to /etc/systemd/system/getty@tty1.service, which contains two non-default lines: ExecStart=-/sbin/agetty %I 38400 --noclear TTYVTDisallocate=no Default omits --noclear and has yes for ...allocate. cf. bug 721660 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c1
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c2
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c3
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c4
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c5
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c6
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c7
--- Comment #7 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c8
--- Comment #8 from Felix Miata
With Xserver being started via startx (no longer supported since how many years now?) it grabs the first available tty, whereas KDM/GDM apparently prefer to chose a predefined tty for the first, second, etc. Xserver.
First available is never tty[1-6] when sysvinit-init is installed, so it seems systemd must be failing to do something sysvinit does do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c9
--- Comment #9 from Frederic Crozat
First available is never tty[1-6] when sysvinit-init is installed, so it seems systemd must be failing to do something sysvinit does do.
I already written it : systemd doesn't handle on which tty X is being started. The only reason X might not start on tty7, compared to sysvinit, might be because tty2-6 are allocated on demand by systemd (when alt-Fx is pressed) and this might screw the logic in X (or display manager) to find a free tty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c10
--- Comment #10 from Felix Miata
tty2-6 are allocated on demand by systemd (when alt-Fx is pressed)
Why the difference here from sysvinit? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c11
Jörg Mayer
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c12
--- Comment #12 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c13
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c14
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=768788
https://bugzilla.novell.com/show_bug.cgi?id=768788#c15
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com