Mailinglist Archive: opensuse-bugs (4233 mails)

< Previous Next >
[Bug 1020327] [Build 20170116] openQA test fails in consoletest_finish
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 23 Jan 2017 11:09:28 +0000
  • Message-id: <>

--- Comment #18 from Franck Bui <fbui@xxxxxxxx> ---
(In reply to Fabian Vogt from comment #17)
(In reply to Franck Bui from comment #16)

Now with v232, systemd-setup-console.service has RemainsAfterExit=false. I
don't know if this change is correct or not but it has the downside to start
one more time systemd-setup-console.service lately during the early boot.

This is incorrect and needs to be changed back (or the service must not be
started at all) AFAICS.

The service is *only* started because plymouth is pulling it.

Once a console got configured, it stays configured.

This assertion is false in both case (v228 and v232). The console is configured
several times by udev because it receives a "add/remove/add" sequence for one

And most important any application is not supposed to *crash*.

And this new console configuration seems to confuse plymouth for some reason
and makes it crash.

Even if configuring the console several times is not nice, I don't think
plymouth is supposed to crash in anyways (BTW I think there is already a bug
open for the crash of plymouth) and this bug should be fixed.

@Fabian, in comment #11, you reported that plymouth git master (and also the
version in Base:System) has a fix for preventing plymouth from crahsing.

So my suggestion here is to fix plymouth by either upgrading Base:System to
git master or by identifying the fix and backport it to Factory.

I already requested that, zaitor had an update already prepared and now
submitted it as sr#451329.


In the meantime I think we could also drop the
Wants=systemd-setup-console.service from plymouth-start.service because
setup-console is supposed to be done via a udev rule (which shouldhappen
before plymouth is started).

@Fabian, WDYT ?

udev alone is not enough, otherwise the .service wouldn't be needed at all.

udev should be enough. The .service is mostly useless now (I think no other
service is requiring it but plymouth).

When the service fails, bugs like 927250 and its three dups happen.
(Or the udev behaviour is buggy, in which case the .service should be removed
entirely, I guess)

I'd proceed this way for now:

- Change back RemainAfterExit in systemd

I'm not sure about this change at all and this should be discussed upstream
first. But IMHO this not the (root) issue here it just exposes the shortcoming
in plymouth.

- Update plymouth to sr#451329

It seems to me the real fix here: plymouth won't be crashing anymore.

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