Red Hat Bugzilla – Bug 968406
[Fedora 19 beta 1] systemd show the login before completing the system load in text mode
Last modified: 2013-06-04 08:58:32 EDT
Created attachment 754473 [details]
Screenshot of the bug, only boot.
Description of problem:
Booting in text mode (removing quiet and rhgb), and appending "3" to kernel cmdline in grub2(legacy mode way for runlevel 3), systemd show the login before that the system is completely loaded with all services, and I can login as root while the system is loaded or at finish but user:password input login is located in the medium of the final load of services.
Version-Release number of selected component (if applicable):
Fedora 19 beta 1
Always, system up to date 29 May 2013
Steps to Reproduce:
1.Install Fedora 19 beta 1
2.Press e in grub2 menu, delete quiet and rhgb, and put 3 in the final of vmlinuz line, and press F10 for boot
3.See the final load of the system, the input login works but is in the medium. systemd show/offer login input before the system load was completed
Minor bug in systemd an login screen for text mode, like a no pulish distro
Attach a screenshot with the bug.
Using traditional rhgb quiet and 3 at the end of the cmdline, works fine and the login is showed *only* after the complete system load.
So, is a systemd bug that is displayed if plymouth/graphical boot is not used.
Considering that much people remove rhgb quiet from /etc/default/grub cmdline for see the boot process and identify services or errors, definitely is a bug not a feature.
In the screenshot, all messages are from the kernel. Do you observe any messages from systemd-started daemons or from systemd itself? getty@ is defined as Type=idle, which means that it should be started after other jobs have finished running .
If only kernel-generated messaged are displayed, there isn't much that systemd can do about it. In fact "NIC Link is Up" can happen at any time, arbitrarily long after boot. By removing "quiet", user explictly requests to see those messages.
Yeah, this isn't really a bug. It's kernel behaviour. Either add "quiet" to the kernel cmdline, or live with these messages.