Cannot enter cryptfs password on boot

Bug #1590692 reported by Heinrich Strauss
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux Mint
Confirmed
Undecided
Unassigned
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

    Version and Edition:
Linux Mint 18 beta (x64; Cinnamon Edition)

    Problem and reproduction and what happened:
When running plymouth (i.e. kernel boot options "quiet splash"), with a seperate /boot partition (~512MB;ext4) and encrypted root (~64GB; ext4 created in installer using Physical Volume for Encryption), the graphical password prompt appears but accepts no input. This is after a dist-upgrade on 2016-06-09 ca. 0200-0400 UCT, with intel-microcode and nvidia-361 custom hardware drivers.

The password text is echoed on terminal 7 (Alt-F7), but does not attempt to unlock the volume. A reboot (Ctrl-Alt-Del) at this point seems to corrupt the partition, which I can boot into using recovery mode, force fsck, resume boot about 50% of the time. Otherwise, a few repeats and I'll be back into the system. (fsck on /, /dev/mapper/sda6_crypt, ext4 does find orphaned inodes, etc)

    Expected:
Password would be accepted in plymouth graphical screen (i.e. echoing dots for password) and system would boot normally after unlocking root partition (/).

    Frequency:
This seems to happen on every boot/reboot, as long as "quiet splash" is in the kernel options. Editing /etc/default/grub and removing the kernel lines shows a text-based password prompt, which unlocks the volume flawlessly. Data corruption still seems to occur on reboot, though.

Changing resolution to 1920x1080 (native panel resolution) does not seem to affect the graphical screen. Only removing the "quiet splash" yields consistent behaviour.

    Hardware:
Dell Latitude E6520 (ca. late-2010), 16 GiB RAM, 240 GiB OCZ Vertex3 SSD, Intel i7-2720QM CPU, nVidia NVS 4200M.

Tags: plymouth
Revision history for this message
AsciiWolf (asciiwolf) wrote :

Same problem here after upgrade from Mint 17.3 to 18.

tags: added: plymouth
AsciiWolf (asciiwolf)
Changed in linuxmint:
status: New → Confirmed
Revision history for this message
AsciiWolf (asciiwolf) 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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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