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
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: /bugs.launchpad .net/bugs/ 538810 /bugs.launchpad .net/bugs/ 554079
https:/
and
https:/