systemd-fsckd starts, flashes the message on how to skip it.
Realiases there are no fscks to run, and exits, without clearing the Ctrl+C imaage.
Then we freeze that output until gdm starts.
Previously, we only flashed "Ctrl+C message" upon receiving the first update from fsck, and cleared it after fsckd exits. This is not happening anymore.
I'm not sure if fsckd is sending the wrong messages, or if plymouth is not processing them correctly.
So i think this is what happens:
systemd-fsckd starts, flashes the message on how to skip it.
Realiases there are no fscks to run, and exits, without clearing the Ctrl+C imaage.
Then we freeze that output until gdm starts.
Previously, we only flashed "Ctrl+C message" upon receiving the first update from fsck, and cleared it after fsckd exits. This is not happening anymore.
I'm not sure if fsckd is sending the wrong messages, or if plymouth is not processing them correctly.