plymouth starts too late since 219-5ubuntu1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
One autopkgtest fails since 219-5ubuntu1. This one checks that plymouth is started around the same time than fsckd, and that fsckd/fsck doesn't fail if plymouth crashes.
The issue comes from debian/
What happens is that:
- systemd-
- udev is thus started later on
- plymouth-
So fsck runs on root FS before udev is up, and so plymouth, the whole boot sequence is delayed.
We have multiple options:
- changing the test to get that use case tested in other ways (in ubuntu, plymouth is started from the initramfs)
- reintroduce the change if we see that udev being started way later is an issue.
Attaching 2 journald boot logs, where we can see the differents time (once with udev/plymouth starting earlier than the other one).
summary: |
- one autopkgtest failure since 219-5ubuntu1 + plymouth starts too late since 219-5ubuntu1 |
Changed in systemd (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Martin Pitt (pitti) |
status: | Confirmed → In Progress |
Fixed in http:// anonscm. debian. org/cgit/ pkg-systemd/ systemd. git/commit/ ?h=experimental &id=0b433ba6d . This will do fine for vivid.