http://bugzilla.opensuse.org/show_bug.cgi?id=1020327
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327#c3
Fabian Vogt changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fabian@ritter-vogt.de
--- Comment #3 from Fabian Vogt ---
I did some investigation on this (based solely on log files though, haven't
tried to reproduce it locally yet).
Before 232:
Dec 30 05:26:27 linux-oikq display-manager[652]: Starting service kdm..done
Dec 30 05:26:27 linux-oikq kdm[695]: plymouth is running
Dec 30 05:26:27 linux-oikq kdm[695]: plymouth is active on VT 7, reusing for :0
Dec 30 05:26:27 linux-oikq kdm[695]: plymouth should quit after server startup
With 232:
Jan 17 03:25:43 linux-oikq display-manager[1412]: Starting service kdm..done
Jan 17 03:25:43 linux-oikq kdm[1507]: plymouth is running
Jan 17 03:25:43 linux-oikq kdm[1507]: plymouth is running
Jan 17 03:25:43 linux-oikq systemd[1]: Received SIGRTMIN+21 from PID 270
(plymouthd).
Jan 17 03:25:43 linux-oikq kdm[1507]: plymouth is NOT running
The SIGRTMIN+21 is a signal from plymouth to systemd, only emitted during quit.
However, kdm didn't tell plymouth to quit yet, which is only the case if it has
not an active vt.
And this is easily confirmed by looking at the video: Plymouth is missing!
As systemd-vconsole-setup takes a whopping 0.5s suddenly (close to 0 before)
it might be related.
One testcase does not fit into this picture though: cryptlvm. As the password
prompt
is displayed successfully by plymouth, it's working fine here (in the initrd,
at least).
However, the journal tells us that systemd-vconsole-setup actually failed here:
Jan 17 00:03:20 linux-qoht systemd[1]: Started Plymouth switch root service.
Jan 17 00:03:20 linux-qoht systemd-vconsole-setup[991]: KD_FONT_OP_GET failed
while trying to get the font metadata: Invalid argument
Jan 17 00:03:20 linux-qoht systemd-vconsole-setup[991]: Fonts will not be
copied to remaining consoles
Jan 17 00:03:20 linux-qoht systemd[1]: Started Setup Virtual Console.
This error does not appear on failing test runs so that seems to indicate that
plymouth only runs successfully iff systemd-vconsole-setup failed.
This is true on all two openQA TW snapshot runs so probably not a conincidence.
Race condition?
Conclusion: Not KDMs fault, as far as I can see.
--
You are receiving this mail because:
You are on the CC list for the bug.