can't enter a password for my encrypted home directory

[ceg]

Binary package hint: mountall

separate bug originally posted as comment https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/456274/comments/34
by Andreas Lieser on 2009-12-06:

I did a fresh Karmic install 2 weeks ago, too, and I still got this bug.

I have two encrypted filesystem (/ and /home) which should be automatically be mounted at boot time. When rebooting I got the splash screen with the following displayed:

Unlocking the disk /dev/sda2 (cryptroot)
Enter passphrase:
cryptsetup: cryptroot setup successfully

This works as expected, but then it fails back to a console:

fsck from util-linux-ng 2.16
/dev/sda1: clean, 171/66264 files, 49686/265040 blocks
fsck from util-linux-ng 2.16
/dev/mapper/cryptroot: 162901/985424 files, 1202649/3937556 blocks
 * Starting init crypto disks...
 * cryptroot (running)...
 * crypthome (starting)
Enter passphrase to unlock the disk /dev/sda4 (crypthome): One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home: waiting for /dev/mapper/crypthome

I can't enter a password for my encrypted home directory (tested several times), and there is no disk activity. I have to press ESC several times to get to the recovery shell:

mountall: Cancelled
init: mountall main process (496) terminated with status 1
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell an re-try.
root@laptop-anl:#:

Then I have to open the crypted home directory manually using "cryptsetup luksOpen /dev/sda4 crypthome", which I have to type in blindly because there is no echo on my console window. Then I get asked for the passphrase, which I put in and after that I continue reboot with "CONTROL-D".

The workaround from #2 (disabling splash at grub) works for me.

Mounting several enrcrypted filesystems with splash enabled worked flawlessly in 9.04 and with a fresh install of Karmic, but stopped working 3 or 4 days ago.

Installed filesets:
mountall 1.0
cryptsetup 1.0.6

[Scott James Remnant (Canonical) (canonical-scott)]

mountall isn't involved in decrypting block devices at all; it only mounts the decrypted device once cryptsetup has created it. If you're not getting a prompt, that's a cryptsetup issue

[Steve Langasek (vorlon)]

cryptsetup does prompt, as shown in the bug description, but the passphrase never reaches cryptsetup. As near as I can tell, this is the same as bug #497684; marking this bug as a duplicate of that one.

[ceg (ceg)]

Sounds good. :)