Unsubscribing sponsors for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885358
Title:
decrypt_gnupg prompt does not accept any keyboard input
To manage notifications about this bug go to:
htt
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
the issue might be fixed with
https://packages.qa.debian.org/c/cryptsetup/news/20160107T035008Z.html
* debian/askpass.c: add plymouth support to the askpass helper
command.
would be worth testing when that version lands in Ubuntu
--
You received this bug notification because you are a member
Thanks for the work, could you maybe send the bug/patch to Debian as
well, since the code seems identic there...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885358
Title:
decrypt_gnupg prompt does
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
** Tags removed: cryptsetup keyfile keyscripts
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885358
Title:
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" ta
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.
** Patch added: "cryptsetup-1.6.6-885358.patch"
https://bugs.launchpad.net/
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.
--
You received this bug notification because you are a me
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 d
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885358
Title:
Also see #122759, which might be related (but provides no fix either).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885358
Title:
decrypt_gnupg prompt does not accept any keyboard input
To manage
11 matches
Mail list logo
