[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system
Rada Emanuel Alexandru
1386005 at bugs.launchpad.net
Wed Feb 22 03:31:18 UTC 2017
i dont was reading all the comentaries (becouse tomor i work, but i was
reading half).
I get the same problem, ubuntu 14.04 and 16.10.
What I was thinking, after all this big bug i want to start my linux in
recovery mode, and then i was searching google how to start in command
line and i get this: http://ubuntuhandbook.org/index.php/2014/01/boot-
into-text-console-ubuntu-linux-14-04/
so I tryed on my Ubuntu 16.10,and work, now i start in command line,
something what give me the chance to type my mda5-crypt password :D
for make this change you can acces the website from up or to do this.
To get started, press Ctrl+Alt+T to open terminal. When it opens, follow the below steps:
sudo gedit /etc/default/grub
Search this
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
change to
#GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
GRUB_CMDLINE_LINUX=”"
change to
GRUB_CMDLINE_LINUX=”text”
#GRUB_TERMINAL=console
change to
GRUB_TERMINAL=console
save the file and type [b] sudo update-grub [/b]
For me is ok.
--
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 Linux Mint:
New
Status in plymouth package in Ubuntu:
Triaged
Status in plymouth package in Arch Linux:
New
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/linuxmint/+bug/1386005/+subscriptions
More information about the foundations-bugs
mailing list