http://bugzilla.suse.com/show_bug.cgi?id=1020327
http://bugzilla.suse.com/show_bug.cgi?id=1020327#c24
--- Comment #24 from Franck Bui
(In reply to Franck Bui from comment #12)
The reason to run systemd-vconsole-setup *before* plymouth is to have a consistent look and feel for any UTF-8 based console font.
If I understood the whole thing correctly, this is already the case and it's ensured by the udev rule, it's not due to plymouth-start using Wants=systemd-vconsole-setup.servcice.
And clearly this has to be redone for every new virtual console but *after* plymouth as otherwise the change(s) will never occure do pylmouth holds a lock on the system console.
If a *new* vtconsole is appearing while plymouth is running then the udev rule is supposed to configure it first. That's done even before plymouth is aware of the new device.
Also I'd like to see the the patch from attachment #709502 [details] would become part of systemd, compare with bug #1019255
You know the procedure ;) And IIRC this patch was about optimization and wasn't a "real" fix. If it fixes an issue then it's more likely a workaround due to timing change or something else. In any cases could you submit it to upstream first ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.