Comment 29 for bug 559761

Folks,

This issue is still present with the following versions:

plymouth: 0.8.2-2ubuntu1
mountall: 2.15~ppa1

Fsck progress displayed at boot screen stops advancing at 70%.
20 seconds after that the login screen appears.

Meanwhile mountall keeps logging: "mountall: Plymouth command failed" on console.
Mountall is still running after login and is busy removing outgoing events (see comment #18) on the following stack trace after it has noticed that the socket towards plymouthd has been closed.

#0 0x00007f2b3c5d06e3 in ply_list_find_node () from /lib/libply.so.2
#1 0x00007f2b3c5d0933 in ply_list_remove_node () from /lib/libply.so.2
#2 0x00007f2b3c3c3c64 in ?? () from /lib/libply-boot-client.so.2
#3 0x00007f2b3c3c3d9e in ?? () from /lib/libply-boot-client.so.2
#4 0x00007f2b3c5cd24b in ply_event_loop_process_pending_events ()
   from /lib/libply.so.2
#5 0x00007f2b3d262482 in nih_io_handle_fds () from /lib/libnih.so.1
#6 0x00007f2b3d263f0f in nih_main_loop () from /lib/libnih.so.1
#7 0x000000000040e2d4 in main (argc=3, argv=0x7fff1f547d78) at mountall.c:3313

To repeat: touch /forcefsck && reboot

This x86_64 host was upgraded from 9.10.

Workaround: Remove the assertion causing time-quadratic behaviour from ply_list_remove_node(), and make mountall less verbose when it fails to issue plymouth commands.
--
tmo