decrypt_gnupg prompt does not accept any keyboard input

Bug #885358 reported by zik on 2011-11-02
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)

Bug Description

I have the boot partition and grub on a USB stick. Unlocking the HDD partition by passphrase works fine, but if I switch to GPG unlocking with a symmetric key, the GPG passphrase prompt does not accept any input. I can switch to the splash screen and back and to other consoles. On switching, the dialog ("Enter your GPG passphrase") gets reprinted, but still does not accept any input.

sda2_crypt UUID=... /etc/keys/cryptkey.gpg luks,keyscript=decrypt_gnupg

/dev/mapper/vol01-root / ext4 noatime,nodiratime,discard,data=ordered,errors=remount-ro 0 1
/dev/disk/by-label/bootstick /boot ext4 defaults 0 2
/dev/mapper/vol01-home /home ext4 noatime,nodiratime,discard,data=ordered 0 2

Ubuntu 11.10, Kernel 3.1.0-030100-generic, cryptsetup 2:1.1.3-4ubuntu2

zik (zikzik) wrote :

Also see #122759, which might be related (but provides no fix either).

Launchpad Janitor (janitor) wrote :

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

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
Nathan Fish (nfish-e) wrote :

I am attempting to set up a similar solution, and have run into the same problem.
I tried removing "quiet splash" from the kernel command line, in case it was blocking the tty. That didn't work, so I disabled plymouth, (moved /bin/plymouth to plymouth.old, since apt-get wasn't working) which didn't help either.

I am using Linux Mint 16, but I don't think that makes a difference, especially since this bug has been open since 2011 for some reason?

Dirk T (miriup) wrote :

I just found a workaround. The boot screen is linked to vt7, that's where I'm asked for the passphrase. Keyboard input is taken from vt1. So when I switch to vt1 (ALT+F1), enter the password there and press ENTER and boots up as expected.

Dave Pifke (dpifke) wrote :

I created the attached patch, which fixes this problem by using plymouth to prompt for the password, if it is available. If plymouth is not available, it defaults to the old behavior of using /lib/cryptsetup/askpass.

The attachment "cryptsetup-1.6.6-885358.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Changed in cryptsetup (Ubuntu):
importance: Undecided → Medium
tags: added: oneiric
removed: cryptsetup keyfile keyscripts
Sebastien Bacher (seb128) wrote :

Thanks for the work, could you maybe send the bug/patch to Debian as well, since the code seems identic there...

Sebastien Bacher (seb128) wrote :

the issue might be fixed with

   * debian/askpass.c: add plymouth support to the askpass helper command.

would be worth testing when that version lands in Ubuntu

Iain Lane (laney) wrote :

Hi Andy, are you handling the plymouth merge that you are TIL for? Seb's comment #8 says that it looks likely to fix this bug which is in the sponsor queue.

Daniel Holbach (dholbach) wrote :

Unsubscribing sponsors for now.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers