+ KEYSCRIPT=plymouth ask-for-password --prompt + echo -e Unlocking the disk /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 (sda2_crypt)\nEnter passphrase: + keyscriptarg=-e Unlocking the disk /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 (sda2_crypt) Enter passphrase: + PARAMS= --key-file=- + [ 0 -lt 3 ] + [ -n plymouth ask-for-password --prompt ] + plymouth ask-for-password --prompt -e Unlocking the disk /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 (sda2_crypt) Enter passphrase:
Hmm, well, this part is a bashism I introduced, oops :/ I'll get that fixed ASAP. Do you want to test whether replacing "echo -e" with "printf" here in /lib/cryptsetup/cryptdisks.functions, to see if that solves your problem? + cryptsetup --key-file=- luksOpen /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 sda2_crypt_unformatted error: unexpectedly disconnected from boot status daemon Hmm, this is a concern, showing up in log.enable - but it could be down to the known lack of locking between these jobs; if the -udev job gets there first (as expected), and successfully unlocks the disk, the -enable job will still be waiting for input when the boot finishes and plymouth shuts down. So I guess that doesn't explain the problem, either. Please check whether s/echo -e/printf/ fixes this. If it doesn't, then we'll have to dig some more. -- [lucid] Plymounth not asking for passphrase on non-root partition https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
