I agree with your diagnosis. It looks like ply_boot_client_flush() is blocking on a write() to plymouthd, which is blocking on a write() back to the process calling that, because the former function only flushes pending writes (in a blocking way) without reading responses
I'd say then that the bug is in libply-boot-client, and that ply_boot_client_flush() should instead be called in such a way that replies are dealt with ** Summary changed: - Graphical bootstrap hangs on fsck + ply_boot_client_flush() does not read replies (plymouth stuck during/after filesystem check or error) -- 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
