Where does this bug with fsck come from? Maybe the file the password is read from (/dev/.initramfs/usplash_outfifo) isn't empty but filled with the output of fsck? If so, why can't you just empty it before prompting for the password and then reading it? "cat" will block if (as it should be) there's no line or byte to read from the file. I don't know, if there's any commandline tool to do this properly, but something like this works:
sudo -s echo -e "some stupid input just to have something within the file" > /dev/.initramfs/usplash_outfifo cat -u /dev/.initramfs/usplash_outfifo So maybe we can put something like this right before prompting for the password in order to empty the file the password is read from. -- "Enter passphrase" for LUKS/cryptsetup breaks usplash https://bugs.launchpad.net/bugs/139363 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
