[lucid] Plymouth/cryptsetup not prompting for passphrase leads to non-mounted /home

Sometime I see:
 sda2_crypt (starting)

On top of the splash, some others I seem to hit a race condition where I just get to a blank screen and need to reboot without splash so it gets me a X server (and console so I can mount my /home manually).

(Race conditions are quite likely on this hardware as it's a relatively fast Core2 CPU and running on Intel X25-M G2 SSD)

You have /home marked noauto in /etc/fstab, so gdm doesn't wait for it before starting, killing plymouth in the process. If you remove this 'noauto' option, you should find that plymouth prompts for a passphrase and that the system waits for it to be entered before starting gdm.

Good catch.

I just tried without the noauto (that I didn't remember of) and now it's stuck at the splash.
Typing the key doesn't make any difference, booting in text mode correctly prompts for the passphrase but doesn't seem to take any input.

I'm experiencing a similar problem with a different configuration. The system hangs sometime after entering the key in a normal boot. If I perform a recovery boot it appears to hang because the key prompt is on tty7. Another oddity is that as I enter the key, it seems like a newline gets printed after each keystroke which causes a new prompt line to appear although it still accepts the key.

Same/similar problem here:

I have ext4 on lvm2 on luks on md

/dev/sdb1
/dev/sdc1

  /dev/md0

    /dev/mapper/crypt_volume (luks aes 256)

      /home (ext4)

worked 100% on jaunty. at boot, normal progress bar shows. then the bar pauses, and password prompt shows asking for crypt_volume as expected. (also note that swap is on /dev/urandom generated luks and is automagically created)

installed lucid. disaster.

at boot, ?plymouth? has blue/white/navy colored overlapping bars moving across bottom of screen.

then it may or may not prompt for input... and the prompt is nonsensical.

i can change to alt-f1 console sometimes to see more info.

i can type characters and get same newline behavior mentioned by jhansonxi on 2/12.

but it never works.

  keyboard LEDs for caps and numlock do not work either.

sometimes hard lock. sometimes screen freezes, but cursor and bars flash rapidly. sometimes i can keep entering keystrokes.

eventually had to mount livecd and disable crypt mounts in etc/crypttab and etc/fstab

is there any test i can do to make this bug progress?
It's almost been a month since the last update.

i have almost the same setup.

/dev/sda1 : 20G ext4 mounted as /
/dev/sda2 : crypto_LUKS
/dev/mapper/sda2_crypt : 100 G ext4 mounted as /home

When i boot i have to enter the password to decrypt /dev/sda2
but then it hangs waiting for /home

This may be related to bug #527666. Please install mountall 2.10 when it's built and see if that fixes the problem you're having.

mountall 2.10 fixed this issue.
Confirmed with both stgraber and me.