You broke the encryption password screen at boot. Again.

[Josh]

This happens every time I upgrade between major versions of Ubuntu regardless of which computer I do it on.

This has been happening on every computer I install Ubuntu on going all the way back to Warty.

Every time there's a new distro upgrade I have to report this bug, wait around while you guys hem and haw, close the bug a few times, accusing me of being an idiot user, then around the fifth or sixth time I open a new bug reporting the problem you eventually get tired of closing bugs and investigate the problem. Then you go "Oh! Look, there really is a problem." Then a few days later an update shows up on my computer that fixes the problem.

When I upgrade from 10.4 to 10.10 and I have full-disk encryption on the system drive, the next time I start up the cursor is not in the password box where I'm supposed to type the password so I can't type the password I'm being prompted for to boot.

I have to go into recovery to skip the graphical boot screen, select "continue booting" from the menu, wait for I guess about five minutes to make sure Ubuntu is done doing things and is ready for my password, then blindly type my encryption password because the password prompt in this boot mode is there, but not visible.

Can we please just skip the closing the bug six or seven times this time and just fix the problem right away?

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-release-upgrader-core 1:14.10.9
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Oct 23 20:52:52 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-05 (18 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to utopic on 2014-10-21 (3 days ago)
VarLogDistupgradeTermlog:

[Adolfo Jayme Barrientos (fitojb)]

What does this have to do with ubuntu-release-upgrader?

[Cepheid (cepheid)]

I could fix this on my computer like this:

Summary:
In /etc/default/grub, I edit the options so that plymouth is not used.

Details:

sudo nano /etc/default/grub

Then: edit the following parameter to the new value noplymouth

GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"

After that, you must run update-grub:
sudo update-grub

Result: Plymouth is not used any more at startup and you can enter the passphrase in text mode.

[Steve Langasek (vorlon)]

> GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"

I have no idea why that would help you, as that is not a recognized boot option.

[Cepheid (cepheid)]

I had the noplymouth option from the German ubuntuusers wiki page:
http://wiki.ubuntuusers.de/Plymouth
and actually, this worked on my computer.

[Steve Langasek (vorlon)]

On Mon, Oct 27, 2014 at 04:49:58PM -0000, G. wrote:
> *** This bug is a duplicate of bug 1386005 ***
> https://bugs.launchpad.net/bugs/1386005

> I had the noplymouth option from the German ubuntuusers wiki page:
> http://wiki.ubuntuusers.de/Plymouth
> and actually, this worked on my computer.

That wiki page shows *replacing* the 'splash' boot option with 'noplymouth'.
This has the effect because you've removed 'splash'. "noplymouth" means
nothing.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mathieu Trudel-Lapierre (cyphermox)]

Reverted the duplicate so I can resolve this once and for all.

Josh, could you attach the entire contents of /etc/default/grub here? We need to make sure whether the file has diverged from a "default" install; since it could be the cause for the bugs.

Noting (for myself) that there should be a dist upgrade test done on nvidia hardware too once /etc/default/grub is available, to try to reproduce the failure.

[Mathieu Trudel-Lapierre (cyphermox)]

Re-prioritizing to Medium; until we know it affects more people, that it's a common issue on upgrade, etc. I'll bump the priority up if necessary.

Alberto, please don't blindly prioritize all plymouth bugs as Critical: they are not all critical even if they affect booting.

[Mathieu Trudel-Lapierre (cyphermox)]

I believe I asked for the history of the previous similar bugs from Josh, to have an idea what had to be fixed before, but I did that on the bug this was marked a duplicate of.

Josh, if you could still provide the list of your previous bugs for such upgrades breaking the encryption password entry, that would be very helpful, in the meantime I'll set this Incomplete so I can get the notifications when you reply.

Thanks!

[Launchpad Janitor (janitor)]

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]