[Bug 1028717] New: Text mode login prompt shortly appears when booting to graphical system
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717 Bug ID: 1028717 Summary: Text mode login prompt shortly appears when booting to graphical system Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: wbauer@tmo.at QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- When booting to a graphical desktop, a text mode login prompt appears for a short while before the graphical login screen shows up, with sddm and xdm at least. The reason is that the function plymouth_quit() is called before the displaymanager is started so that plymouth doesn't block the VT. That's the case at least with xdm, sddm, and lightdm; kdm and gdm handle plymouth themselves... This is mainly a cosmetical issue, but I also heard of users getting confused and thinking they have to login to text mode to get to a graphical system (because that's what they experienced: they logged in in text mode, and then the graphical desktop started). On the sddm side we are intending to improve things by calling "plymouth quit --retain-splash" instead of plymouth_quit (in Factory/Tumbleweed only for now), but the same change may be a good idea for the standard displaymanager script too. For the record, I tried xdm with that change and it started up fine here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c1
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c2
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c3
--- Comment #3 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c4
--- Comment #4 from Stefan Dirsch
The reason why we didn't use that parameter is because if anything after it fails, we're left with neither a graphical nor a text based interface (though Ctrl-Alt-F1 is probably still possible).
Thanks. Understood. And for me this is indeed a *very* valid reason. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c5
--- Comment #5 from Wolfgang Bauer
The reason why we didn't use that parameter is because if anything after it fails, we're left with neither a graphical nor a text based interface (though Ctrl-Alt-F1 is probably still possible).
Ah ok. I didn't think about that case I have to admit. (maybe because switching to VT1 from the running login screen did show a login prompt in text mode...) But yes, this is indeed a problem, also with sddm. On my real system here (radeon) not even Ctrl-Alt-Fx helps then (the screen stays blank with just a blinking text cursor), though in vmware it does. So my original proposal (by itself) doesn't seem to be a good idea after all... Sorry. (In reply to Max Staudt from comment #3)
In case that doesn't work or doesn't seem like a good idea:
Maybe a workaround would be to switch to an unused VT before running the display manager?
Hm. I thought that is done already/still. (the DM normally runs on VT-7) But maybe it would be possible somehow to reset the VT in the display-manager script in case the DM fails to start? Just a thought... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717#c6
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1028717
Stefan Dirsch
participants (1)
-
bugzilla_noreply＠novell.com