Comment 0 for bug 577331

Binary package hint: plymouth

PROBLEM

There seems to be no way to skip an fsck with plymouth.

TEST CASE

1. sudo touch /forcefsck && sudo reboot

2. While fsck is in progress, press c

3. press i for ignore

* Plymouth locks up and reboot is required

OBSERVATIONS

Currently, and in my case, to be able to get to the cancel screen at all, c must be pressed almost immediately as plymouth splash is initiated, due to Bug #571707 which makes plymouth stall otherwise.
If using the patched packages available for said bug, it seems to be possible to cancel at any point during the fsck (there is still a considerable delay between the keypress and the cancel screen though), but the issue in this bug remains otherwise.

Message when c is pressed says "Serious error was encounterd"; cancelling an fsck does not inherently cause errors, does it? This is a case of very bad wording to me.

Trying to skip mounting (pressing s) after cancelling fsck locks up plymouth with the message "waiting for /tmp" Is this the right way to handle this? Should the option to skip mounting the root filesystem even exist as an option?

Dropping to maintenance shell with m works as expected, but only if plymouth hasn't already locked up by any of the other options