plymouth doesn't say which luks passphrase it wants

Bug #1293141 reported by Mike Doherty
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have two additional encrypted filesystems which are mounted at boot. For the first one, I'm prompted "The filesystem for $mount_point is unavailable... enter passphrase for /dev/mapper/encrypted_vol". Once the passphrase is entered, the text box empties, but no other text on the screen changes. I've deduced that this is the prompt for the second filesystem's passphrase, and indeed entering the passphrase at this time works. Boot continues, and both filesystems were mounted. But obviously, the text should change to indicate which filesystem is unavailable, and which volume to enter a passphrase for.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu8
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun Mar 16 12:13:51 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
InstallationDate: Installed on 2013-01-12 (427 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: TOSHIBA TECRA R700
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-18-generic root=/dev/mapper/ubuntu-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-18-generic root=/dev/mapper/ubuntu-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to saucy on 2013-10-23 (143 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 2.20
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.20:bd12/22/2011:svnTOSHIBA:pnTECRAR700:pvrPT318C-00F001:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA R700
dmi.product.version: PT318C-00F001
dmi.sys.vendor: TOSHIBA

Revision history for this message
Mike Doherty (doherty) wrote :
Revision history for this message
Mike Doherty (doherty) wrote :

/etc/crypttab:
...
crypt_usr-store /dev/ext0/usr-store none luks,noearly,checkargs=ext4
crypt_backups /dev/ext0/backups none luks,noearly,checkargs=ext4

/etc/fstab:
...
/dev/mapper/crypt_usr-store /mnt/usr-store ext4 defaults,errors=remount-ro,nofail 0 2
/dev/mapper/crypt_backups /mnt/backups ext4 defaults,errors=remount-ro,nofail 0 2

Revision history for this message
Mike Doherty (doherty) wrote :

I've remembered the prompt incorrectly.

The first prompt is as I described. For the second prompt, the text saying which filesystem is unavailable does change. But plymouth still says "Unlocking the disk /dev/mapper/the_first_volume" instead of updating to reflect the volume that is really being unlocked this time.

I will upload a video shortly.

Revision history for this message
Mike Doherty (doherty) wrote :
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.