https://bugzilla.suse.com/show_bug.cgi?id=1218618 https://bugzilla.suse.com/show_bug.cgi?id=1218618#c7 Martin Wilck <martin.wilck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck@suse.com --- Comment #7 from Martin Wilck <martin.wilck@suse.com> --- Created attachment 871726 --> https://bugzilla.suse.com/attachment.cgi?id=871726&action=edit journal excerpt from my system Not exactly what you asked for I guess, but perhaps helpful nonetheless: You can see that systemd-vconsole-setup.service is started 7 times and stopped 4 times during a single boot. The first start (in initrd) seems to work. [ 1.218872] apollon systemd[1]: Starting Virtual Console Setup... [ 1.355556] apollon systemd[1]: Finished Virtual Console Setup. IMHO, this should be perfectly sufficient for setting up the VC, and no additional invocations of this unit would be necessary, neither in initramfs nor afterwards. Is that wrong? After that, plymouth starts, and we see various stop messages [ 2.370086] apollon systemd[1]: systemd-vconsole-setup.service: Deactivated successfully. [ 2.374073] apollon systemd[1]: Stopped Virtual Console Setup. [ 2.374364] apollon systemd[1]: Stopping Virtual Console Setup... [ 2.404866] apollon systemd[1]: Starting Virtual Console Setup... Then this: [ 2.681190] apollon systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, ... I am assuming this is because plymouth wants to persist over the switch root step. Not sure if systemd nowadays provides cleaner methods to achieve this. systemd-vconsole-setup.service is started once more, and fails now: [ 4.340640] apollon systemd[1]: Starting Virtual Console Setup... [ 4.749467] apollon systemd-vconsole-setup[588]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument [ 4.749841] apollon systemd-vconsole-setup[588]: Fonts will not be copied to remaining consoles [ 4.750962] apollon systemd[1]: Finished Virtual Console Setup. System switches root, and we see the surviving plymouthd: [ 6.220795] apollon systemd[1]: Switching root. [ 7.333967] apollon systemd[1]: plymouth-start.service: Unit process 402 (plymouthd) remains running after unit stopped. [ 7.354857] apollon systemd[1]: Stopped Show Plymouth Boot Screen. [ 7.355152] apollon systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid). More vconsole weirdness: [ 10.449820] apollon systemd[1]: systemd-vconsole-setup.service: Deactivated successfully. [ 10.521052] apollon systemd[1]: Stopped Virtual Console Setup. [ 10.521179] apollon systemd[1]: Stopping Virtual Console Setup... [ 10.531692] apollon systemd[1]: Starting Virtual Console Setup... [ 10.542832] apollon systemd-vconsole-setup[972]: No usable source console found: Device or resource busy [ 10.609910] apollon systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE [ 10.610049] apollon systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. [ 10.662732] apollon systemd[1]: Failed to start Virtual Console Setup. This is the actual error reported here; my guess is that it happens because the surviving plymouth process with PID 402 has the console grabbed. This pattern repeats until plymouth finally exits. [ 52.646923] apollon systemd[1]: Finished Hold until boot process finishes up. I started systemd-vconsole-setup.service manually, and now it succeeds, just like the first time: [93288.606387] apollon systemd[1]: Starting Virtual Console Setup... [93288.846104] apollon systemd[1]: Finished Virtual Console Setup. -- You are receiving this mail because: You are on the CC list for the bug.