[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system
Josh
1386005 at bugs.launchpad.net
Tue Oct 28 19:14:09 UTC 2014
I'd like to point out a couple of things that were lost when my bug was
merged with this one:
1. This bug happens every time a distribution upgrade of Ubuntu comes
out. It's been happening since Warty, and I've had to report the problem
and wait a couple of months for a fix every time.
2. Every time this happens you guys are utterly surprised like you've
never seen anything like it, and you poke and prod at the people
reporting the bug to try a bunch of different configuration changes to
see if they can fix the problem themselves. That is not acceptable
behavior.
This creates a number of problems:
1. You're treating Ubuntu like it's Joe Distro, your average linux
distribution that is thrown together by some bored computer nerd in
their basement for fun in between raids in World of Warcraft, or
whatever game it is kids are playing these days. But the reality is that
Ubuntu ships on hardware from OEMs. Actual, real computers and embedded
systems that people buy and expect to work. So when a problem like this
happens to the average user who is not technically astute in
troubleshooting a complex operating system, this means that a bunch of
people are going to restart their computer and go "huh, I can't log in.
I enabled encryption and now my computer doesn't work. I don't trust
this OEM anymore."
2. This is a repeating, critical problem. This isn't a problem that
prevents you from browsing the web or from playing games, it completely
disables access not only to your operating system but to all of your
files as well. How you guys can see this happen once and not have some
process in place to check that it doesn't happen with the next build is
beyond me; how you can let it happen every single time there's a new
version out is preposterous.
For every Ubuntu user who reports this problem there are hundreds who
don't understand what's going on and just think their computer is
broken.
How are they even supposed to use ubuntu-bug if their computer won't
start?
This should be a P0 bug because anyone who experiences this problem has
a critical issue but you're treating it with the same level of
importance as a minor inconvenience.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1386005
Title:
Password not accepted graphical boot for encrypted root system
Status in “plymouth” package in Ubuntu:
Confirmed
Bug description:
After upgrading to 14.10 from 14.04, I am unable to enter my password for decypting the root filesystem. The password is echoed in plaintext on the graphic boot screen and does not show up in the password entry box on the graphic. In order to boot the system, I have to boot in recovery mode and enter the password during the text mode boot. This problem was also described by another user in problem# 1385027. I did not have a probem in 14.04. I am using nvidia drivers. I am set to resolution 1920x1200. I am running module uvesafb with changes to /etc/default/grub for the module and resolution. I assume this is a plymouth package bug but am not positive.
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 14.10
InstallationDate: Installed on 2014-04-21 (189 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E6500
NonfreeKernelModules: nvidia
Package: plymouth 0.9.0-0ubuntu7
PackageArchitecture: amd64
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hogwarts_vg-root ro recovery nomodeset
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hogwarts_vg-root ro recovery nomodeset
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Tags: utopic
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.13.0-37-generic x86_64
UpgradeStatus: Upgraded to utopic on 2014-10-23 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.name: 0PP476
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA27:bd12/06/2011:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0PP476:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005/+subscriptions
More information about the foundations-bugs
mailing list