Comment 27 for bug 554737

The problem still exists for me. However, in my case, no plymouth processes were present after booting, even though mountall failed to terminate (see comment 23 above). The only difference I have observed is that KDM is running on a different console.

Booting the 2.6.32-20 kernel with 'nosplash' option, setting high mount count on an ext3 partition with tune2fs prior to rebooting.

Before upgrade: plymouth:
Plymouth version: 0.8.1-4ubuntu1
"mountall: Plymouth command failed" scrolling on VT1
KDM loading on VT8

After upgrade:
Plymouth version: 0.8.2-0ubuntu1~ppa2
"mountall: Plymouth command failed" scrolling on VT1
KDM loading on VT7