Mountall hangs or appears to hang when usplash running, waiting for dependant mounts and esc pressed.

Binary package hint: mountall

Mountall in Ubuntu Karmic (version 1.0) hangs or appears to hang when usplash running, waiting for dependant mounts and esc pressed.

I have the following dependant mounts in my /etc/fstab:

/home/TMP /tmp ext4 rw,bind,relatime 0 0
/home/VAR_TMP /var/tmp ext4 rw,bind,relatime 0 0
/home/VAR_SPOOL /var/spool ext4 rw,bind,relatime 0 0
/home/VAR_MAIL /var/mail ext4 rw,bind,relatime 0 0
/home/VAR_CACHE_CUPS /var/cache/cups ext4 rw,bind,relatime 0 0

and /home is a partition on a LUKS volume. If I boot with the splash screen and /home
fails fsck, I get the message that the above items cannot yet be mounted, press Esc for
recovery shell-but if I press esc, nothing happens and the machine seems to hand. At least
once on NOT pressing escape, the above message persisted, no reference to filesystem checks
ever appeared in usplash-but the system silently proceeded to fsck /home ( a 10 minute job
on a 144 GB partition) and continue the boot.

On the other hand, if fsck is forced due to /home meeting it's mount quota (set at 30 mounts on the AMD,
none of the laptop), the fsck message appears just as it would for the root partition and the Esc function
works. On the other hand, if you press esc on a ROOT partition check, the progress stops updating but the
boot does NOT seem to continue.

If you press esc during any fsck run on the root partition, or on getting the message about waiting for
devices, you get a hang and will next be pressing RESET. The workaround when this happens is to disable usplash
on the next boot(editing the grub menu instructions on boot, affecting that boot only), as the appropriate fsck
notations will then show on the console.

Here is my complete /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0

#was on /dev/sda1 during installation
UUID=76619619-e600-44fe-95f8-e7a436090b04 / ext4 relatime,errors=remount-ro 0 1
UUID=4899ee08-3653-4eed-8610-86b354b00676 /home ext4 rw,relatime 0 2
UUID=5d260145-f4a4-4723-9fbc-c14ab0e3dde9 none swap sw 0 0
#
/home/TMP /tmp ext4 rw,bind,relatime 0 0
/home/VAR_TMP /var/tmp ext4 rw,bind,relatime 0 0
/home/VAR_SPOOL /var/spool ext4 rw,bind,relatime 0 0
/home/VAR_MAIL /var/mail ext4 rw,bind,relatime 0 0
/home/VAR_CACHE_CUPS /var/cache/cups ext4 rw,bind,relatime 0 0
#
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy vfat rw,noauto,user,sync 0 0
#

Here is the associated /etc/crypttab:

# <target name> <source device> <key file> <options>
vgbase UUID=8a3eca01-b07b-43c5-ba8a-34f0e8749662 none luks,tries=3

The splash screen is a custom compiled variation on the Ubuntustudio splash warning that all files are encrypted, with -v
hardcoded into /usr/share/initramfs-tools/scripts/init-top/usplash. Here is the edited line from that script:

 /sbin/usplash -x 800 -y 600 -v -p -c -t 60 --background --pidfile usplash.pid

This custom splash also requires the older "framebuffer" script in the same directory, as it will hang on the first usplash_write invocation when the newer version changes the video card resolution. It also requires that "verbose"
be set in the script and not in the kernel options, or the passphrase never gets to cryptsetup.

Is anyone else getting the "hang on Esc" bug? If not, I will assume the bug is somehow in my splash compilation-even though only the images are changed(added text and "armed penguins").