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 16:03:02 +0000
  • Message-id: <>

--- Comment #7 from Franck Bui <fbui@xxxxxxxx> ---
Ok, here's my best bet:

Since systemd v232, systemd-vconsole-setup.service has no more the
RemainAfterExit=true property.

Since plymouth-start.service has Wants=systemd-vconsole-setup.service, the
later is now started several time within the initramfs: it's pulled in by
and by And during the second time vconsole-setup is
configuring tty7, which was probably already activated by plymouth-start.

This has the bad effect to "confuse" plymouth as vconsole-setup is now
configuring tty7 after plymouth started using it. This makes actually plymouth

The crashes may happen either right before switching to the rootfs or after. If
the former then systemd will start it again after switching to the new rootfs
otherwise it won't.

Now regarding KDM, not sure if it's expected but it selects:

- tty7 if plymouth is not running (IOW if it crashed after switching
to new rootfs)

- tty8 if plymouth is running (IOW if plymouth crashed before switching
to the new rootfs)

From that, there're a couple issues:

- why does plymouth-start.service wants systemd-vconsole-setup.service:
I don't see the point as vconsole-setup will automatically configure
any tty detected by udev ?

- systemd-vconsole-setup.service is embedded in initramfs and this doesn't
seem to be needed.

- why does plymouth crash in this case (might be fixed in plymouth
git repo as Fabian reported a better behavior on IRC) ?

- Why does KDM select either tty7 or tty8 ? in both case tty7 seems to
have been activated by plymouth ?

I'll add the relevant logs.


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