https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c19 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #19 from Felix Miata <mrmazda@earthlink.net> 2013-03-13 01:27:13 UTC --- Bug 803471 is NA here. Can't some artificial depends be placed in rc-local.service or elsewhere to ensure long enough wait before getty@tty1.service starts, maybe agetty itself, or getty, or numlock? As a sort of workaround, what about a user configurable fixed length wait for tty1, but allowing tty[2-6] availability as soon as everything agetty requires has finished? I rarely log in on tty1 anyway, reserving it for the boot messages until such time as may come that I need more than 5 ttys doing something at once? You may not want to or be able to fix it any time soon, but that doesn't make it resolved or fixed, much less unfixable. NAICT, Plymouth is not an essential element of the 12.3 init process[1], and so shouldn't be depended upon to provide function or user experience no worse than that of the init system it supplanted. If if won't be fixed while 12.3 remains supported, then leave it open for future attention. Don't indicate to potentially interested parties who might do what you can't or won't by closing as fixed. http://lists.fedoraproject.org/pipermail/devel/2013-March/179848.html -- 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.