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.
** Changed in: plymouth (Ubuntu Focal)
Status: Invalid => New
** Changed in: plymouth (Ubuntu Groovy)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880250
Title:
disk check progress no longer visible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
