Comment 76 for bug 1238194

When I installed 14.04 TLS I had enabled sda5_crypt. Last year I did the upgrade from 14.04 TLS to 16.04 TLS.

And today, I don't think anything bad, I install the latest kernel version .59 or similar, by use of synaptic (well it's comfortable to me, too). When I do reboot the system it hangs at "Please unlock disk sda5_crypt:". I type in the password. And then I press the [enter] key on the keyboard. But nothing happins. I do a reboot and I try it again, and again, and again, and again. How boring, how stupid. At luncgh time I think something is wrong. I find this thread and so *uck the *ell. I'm wondering, a thread starting in 10/2013 and today is 01/2017. My job is tester software, and sometime it's not easy and actually I have a lot of headache, 'cause my productive system isn't usable anymore. I won't recommend in the future to install sda5_crypt on any system and I will recommend to delete it on any system, too.

I take a look on the entries for this issue begin at #68. But for me 'nosplash' is always enabled in the GRUB entries. I don't think the issue is in relation with the splash. I use the >e< option at booting and use the emacs editor to inspect/review the GRUB entries.