There is also a possible additional duplicate of this, as bug #559761. In that case, the mountall process remains after boot, using 100% CPU time. However, there are no plymouth processes running at the time. I have attached a backtrace of the mountall process to comment 8 of that bug.
-- ply_boot_client_flush() does not read replies (plymouth stuck during/after filesystem check or error) https://bugs.launchpad.net/bugs/554737 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
