Comment 32 for bug 554737

Revision history for this message
ingo (ingo-steiner) wrote :

Checked again:

fsck is definitely not finished: file /forcefsck is not erased!

So it is not just killing plymouth, start-up procedure is faulty. See also this bug report:
https://bugs.launchpad.net/bugs/538810
and
https://bugs.launchpad.net/bugs/554079