Mailinglist Archive: opensuse-bugs (4233 mails)

< Previous Next >
[Bug 1020327] [Build 20170116] openQA test fails in consoletest_finish
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 18 Jan 2017 08:58:41 +0000
  • Message-id: <bug-1020327-21960-xlvKDGpXwg@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327
http://bugzilla.opensuse.org/show_bug.cgi?id=1020327#c4

--- Comment #4 from Franck Bui <fbui@xxxxxxxx> ---
(In reply to Fabian Vogt from comment #3)
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!


I'm not sure to understand.

Basically if KDM notices plymouth is active on tty7 then it reuses the terminal
otherwise KDM selects tty8 instead of tty7 (which should be free).

Could you explain the logic here ?

Just in case, plymouth is required to quit once systemd reached
"graphical.target".

$ systemctl cat plymouth-quit.service
# /usr/lib/systemd/system/plymouth-quit.service
[Unit]
...
Conflicts=graphical.target

and display-manager.service uses Type=Forking (not sure why).

So depending on how KDM is ordered and when exactly it's started during the
boot, it might or not see plymouth running. This probably explains why we see
different behaviors.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References