passphrase input-box for encrypted disk is not shown

Bug #1530548 reported by sudodus
This bug report is a duplicate of:  Bug #1359689: cryptsetup password prompt not shown. Edit Remove

This bug report was converted into a question: question #639553: passphrase input-box for encrypted disk is not shown.

30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Critical
Unassigned

Bug Description

Iso-testing Lubuntu Alternate i386 iso file, testcase 'Alternate Install (Encryption) in Lubuntu Alternate i386 in Xenial Xerus Daily (alias Alpha1 in this case)

The bug appears in the installed system:

The passphrase input-box for encrypted disk is not shown (and the plymouth dots are not shown either, only a dark blue background). Pressing some of the

ctrl + alt + (F1-F7) keys

and after that

Escape

brings a text screen with the text 'Please unlock disk sda5_crypt', and it is possible to enter the passphrase, and I arrive at the login screen.

(Otherwise the encrypted disk and also encrypted home work.)

*****
A better workaround (than hitting ctrl+alt+(F1-F7) keys and then Escape)
is to remove the boot options 'splash $vt_handoff'

You can do it 'live' after pressing the left shift key during boot and then the 'e' key.

-o-

You can actually enter the passphase while the dark blue screen (in Lubuntu) is displayed (without any help text and without feedback stars or dots). But it is confusing and would make most users think that the boot has failed. I did not think of it until I had a nights sleep ;-)
*****

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: plymouth 0.9.2-3ubuntu8
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic i686
ApportVersion: 2.19.3-0ubuntu2
Architecture: i386
CurrentDesktop: LXDE
Date: Sat Jan 2 15:50:33 2016
DefaultPlymouth: /usr/share/plymouth/themes/lubuntu-logo/lubuntu-logo.plymouth
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-01-02 (0 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160102)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.version: PSCBXE-00C00VN5
dmi.sys.vendor: TOSHIBA

Revision history for this message
sudodus (nio-wiklund) wrote :
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1530548

tags: added: iso-testing
sudodus (nio-wiklund)
description: updated
description: updated
Revision history for this message
sudodus (nio-wiklund) wrote :

Maybe this bug is somehow related to Bug #1525044

'after fresh install with encrypted lvm system refuses to get past grub'

Revision history for this message
sudodus (nio-wiklund) wrote :

This bug is also affecting Ubuntu Gnome, iso-testing testcase

'Install (entire disk with lvm and encryption) in Ubuntu GNOME Desktop amd64 in Xenial Daily'

Jan 2 (2016-01-02).

sudodus (nio-wiklund)
description: updated
summary: - passphrase for encrypted disk is not shown
+ passphrase input-box for encrypted disk is not shown
Revision history for this message
sudodus (nio-wiklund) wrote :

This bug appears not only in my Toshiba laptop but also in a Lenovo X131e laptop.

Revision history for this message
sudodus (nio-wiklund) wrote :

This bug appears also in an old desktop computer with an ASUS M2N-VM DVI motherboard and Athlon 64 X2 Dual Core Processor 4400+

Revision history for this message
sudodus (nio-wiklund) wrote :

A better workaround (than hitting ctrl+alt+(F1-F7) keys and then Escape)
is to remove the boot options 'splash $vt_handoff'

You can do it 'live' after pressing the left shift key during boot and then the 'e' key.

-o-

You can actually enter the passphase while the dark blue screen (in Lubuntu) is displayed (without any help text and without feedback stars or dots). But it is confusing and would make most users think that the boot has failed. I did not think of it until I had a nights sleep ;-)

description: updated
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

This seems to me like it's a duplicate of bug# 1370707, no?

Revision history for this message
sudodus (nio-wiklund) wrote :

Maybe, maybe not.

But this bug did not appear until recently (in Xenial), while bug# 1370707 was reported already for Ubuntu 14.10 daily-live image from 17th September 2014.

Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
Changed in plymouth (Ubuntu):
importance: Undecided → Critical
Revision history for this message
masand (markus-sand) wrote :
Download full text (3.7 KiB)

After searching and trying for a long, long time, I finally found a
solution which is acceptable for me. The situation is rather complex, so I
try to describe it as structured as possible.

Configuration
-------------
Hardware configuration:
DH87RL board
i7-4771 CPU
GeForce GTX 970

Software configuration:
Ubuntu 15.10

Driver selection
----------------
You can either go with the open nouveau driver which is installed by
default, or use the proprietary nvidia driver. Next, the "plymouth" package
which enables you to configure the graphical boot up, is strongly involved.
Using the nvidia driver together with plymouth does not work for me, but for
all other 3 possible combinations, the solution is described below.

There are 2 issues here closely connected, one is being able to enter the
password for encrypted hard disks during boot, and the other is being able
to switch to the console when X is up and running. Both issues are described
below.

Being able to enter the password for encrypted hard disks during boot
---------------------------------------------------------------------
Nouveau driver with plymouth:
The Nouveau driver works "ok" - this means I have to press the down arrow on the
keyboard while booting so the text mode appears. There, the password is
asked. (Some stars may already be displayed - delete them before entering the
password...)

This solution was ok, but I needed the nvidia driver to work, because with
nouveau, for example, I had no proper 3D acceleration inside virtualbox.

Nvidia driver without plymouth:
The nvidia driver I use is nvidia-352 currently. I installed it via apt-get.
So I did not download and install the driver from the nvidia.com site
directly, but used the distribution (in my case: Ubuntu 15.10) package for
the nvidia driver instead.

For the nvidia driver to work, I had to disable plymouth. This can be done
for example by passing the "noplymouth" option to the kernel parameters.

--- /etc/default/grub (example) ---
[...]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noplymouth"
[...]

--- update-grub ---
Afterwards, execute update-grub from the command line:
# update-grub

With that changes, I can see the screen flicker shortly during the graphical
boot (obviously the password prompt appearing for a fraction of a second,
and then disappearing again). But now I know that the password
prompt is there, and I can start to type the password. The prompt will
reappear with the first character typed, having recognized the typed
character already.
If insecure whether the password prompt is ready or not, I can still press
the down arrow as described above.

Yes, that´s not a perfect solution - but after searching and trying for such
a long, long time: At least it is working - and you can get used to it.

Just out of curiosity, I also tried the nouveau driver with plymouth disabled:
In that case it works much smoother, as the password prompt really appears
and stays on the screen.

So it seems the free nouveau driver is doing something better than the
nvidia driver. I guess NVIDIA has some homework to do here!

Switch to console
----------------
With the nouveau driver, it is easily possible to switch to the console
(CT...

Read more...

Revision history for this message
Megan Rizzo (megrizzo33) wrote :

WARNING: Signed boot verification is disabled; enabling it for security.
You can disable it again using: sudo crossystem dev_boot_signed_only=0
Installing xenial-armhf chroot to /usr/local/chroots/xenial
Downloading latest debootstrap...
Download from Debian gitweb failed. Trying latest release...
2017-06-01 22:17:29 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/d/debootstrap/ [7115/7115] -> "-" [1]
Downloading debootstrap version 1.0.90...
2017-06-01 22:17:29 URL:http://cdn-fastly.deb.debian.org/debian/pool/main/d/debootstrap/debootstrap_1.0.90.tar.gz [69936/69936] -> "-" [1]
Patching debootstrap...
Downloading bootstrap files...
W: Cannot check Release signature; keyring file not available /usr/share/keyrings/ubuntu-archive-keyring.gpg

Changed in plymouth (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.