[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Launchpad Bug Tracker
1500751 at bugs.launchpad.net
Sun Mar 6 21:51:13 UTC 2016
This bug was fixed in the package initramfs-tools - 0.122ubuntu6
---------------
initramfs-tools (0.122ubuntu6) xenial; urgency=medium
[ Andy Whitcroft ]
* uuids: only apply case mapping to RFC#4122 format uuids (LP: #1553107,
#1548120)
[ Timo Aaltonen ]
* hooks/framebuffer: Copy kernel/ubuntu/i915 backport driver too. (LP:
#1500751)
initramfs-tools (0.122ubuntu5) xenial; urgency=medium
[ Andy Whitcroft ]
* uuids: busybox tr does not support symbolic ranges expand manually
(LP: #1548120)
[ Martin Pitt ]
* wait-for-root.c: Drop check if device is queued in udev (LP: #1539195)
initramfs-tools (0.122ubuntu4) xenial; urgency=medium
[ Manoj Iyer ]
* Add support for uppercase and lowercase uuids. (LP: #1548120)
-- Andy Whitcroft <apw at ubuntu.com> Fri, 04 Mar 2016 10:12:42 +0000
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1500751
Title:
Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Status in cryptsetup package in Ubuntu:
Invalid
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in cryptsetup source package in Trusty:
Invalid
Status in initramfs-tools source package in Trusty:
Triaged
Status in cryptsetup source package in Vivid:
Invalid
Status in initramfs-tools source package in Vivid:
Triaged
Bug description:
I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog.
I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard.
I thought about supplying more information, but things like the syslog
are not helping apparently (I was not able to boot until the syslog
would capture information...). If you need anything I can provide, I
gladly help.
[Test case]
1. On an affected system boot into kernel 3.19.0-30
[Solution]
The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution).
PS.: Bugs like the following are either not applicable or the solution is not working for me:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions
More information about the foundations-bugs
mailing list