Ubuntu
cryptsetup package

13.10 regression: No password asked for encrypted partitions during boot

Bug #1225136 reported by MA
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

# cat /etc/crypttab
home /dev/sda3 none luks

# cat /etc/fstab
...
/dev/mapper/home /home ext4 defaults 0 0

During boot, there's a message that /home isn't ready or not present.
Skip or Manual recovery

Expected: prompt me for password

This works:
cryptsetup luksOpen /dev/sda3 home; mount /home

13.04 used to work with same setup (and it also detected the encrypted partition during install, and set it up for me. 13.10 ignores it)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: cryptsetup-bin 2:1.4.3-4ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Fri Sep 13 21:25:13 2013
InstallationDate: Installed on 2013-09-13 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130909)
MarkForUpload: True
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
MA (mariusa) wrote :
Quinn Balazs (qbalazs)
tags: added: regression-release
Steve Langasek (vorlon)
tags: removed: regression-release
Revision history for this message
Steve Langasek (vorlon) wrote :

What plymouth theme / frontend are you using? I'm able to reproduce an issue like this with plymouth-theme-ubuntu-text: the prompt is shown, but is then almost immediately overwritten when the screen refreshes to show the 'Continue to wait, [...]' message. But if I start typing, it's captured as a passphrase and I'm able to unlock the disk - and all disks are mounted correctly.

So I think this is a bug in the text theme. But I don't see any way that this could be a regression since 13.04, because the text theme hasn't changed since raring. So maybe instead something has changed with your hardware that causes the text splash to be used instead of the graphical splash? Have you recently enabled nvidia/fglrx binary drivers for your system?

Changed in cryptsetup (Ubuntu):
status: New → Incomplete
Revision history for this message
MA (mariusa) wrote :

Hello Steve,

Using the defaults. For grub, I also tried both
GRUB_CMDLINE_LINUX_DEFAULT=""
and
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

My password contains letter "m", and whenever I reach it, it goes into Manual recovery mode.

In 13.04, I also had continue to wait message, but typing password and Enter worked.

Revision history for this message
Steve Langasek (vorlon) wrote :

> Using the defaults.

Yes, but the defaults will result in a different boot experience depending on the hardware and the driver configuration. Are you using binary drivers? Do you get the text experience that I describe - where typing causes the passphrase prompt to show up after having been overwritten - or do you get something else? Is there any chance you could take a picture of what you're getting on boot?

> My password contains letter "m", and whenever I reach it, it goes into
> Manual recovery mode.

Ok, I certainly can't reproduce this. With either the graphical or the text frontend, the passphrase prompt takes precedence over the "press S or M" prompt, as expected/designed.

Revision history for this message
MA (mariusa) wrote :

Here's the photo. Hope it helps!

Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks for the photo. This definitely confirms that the problem is happening with the Ubuntu graphical splash screen. Unfortunately, I definitely can't reproduce this here and there have been no other reports of the problem. Setting the bug back to 'new'.

Changed in cryptsetup (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

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