There are two different bugs being discussed here. 1. The original bug being talked about here, the "fsck clean" message, can be fixed by redirecting the fsck call in /usr/share/initramfs- tools/scripts/functions to /dev/null or something (or *only* saving it to the log).
2. The issue with plymouth not showing at shutdown is related to the recent /run/systemd/fsck.progress patch. Plymouth needs to unlink() that socket on start up or so. To avoid confusion with tracking, I have opened bug 2115286 to track the latter. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2114116 Title: Questing boot splash is interrupted by fsck "clean" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2114116/+subscriptions -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
