Keyboard doesn't work for crypt passphrase on bootup

[mash]

I have to hard reboot and then select a kernel. The keyboard does work for the text-based, i.e., not GUI, entry of the crypt passphrase, and then the boot proceeds.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-28-generic 3.19.0-28.30
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0p: mash 1437 F...m pulseaudio
 /dev/snd/controlC1: mash 1437 F.... pulseaudio
 /dev/snd/controlC0: mash 1437 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
Date: Sat Sep 12 11:57:56 2015
HibernationDevice: RESUME=UUID=00c65b3f-bd60-4cf0-bf05-32e6709d92a1
InstallationDate: Installed on 2015-08-06 (37 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

[mash (mash-econs)]

BTW problem appears trying to boot Linux 3.19.0-29.

I can then boot either -28 or -29 from the text-based selection of the kernel in recovery mode.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

mash, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[mash (mash-econs)]

Thank you for the guidance. I will need a bit more coaching than appears on https://wiki.ubuntu.com/Kernel/MainlineBuilds

First, is the kernel I should test the top one listed on http://kernel.ubuntu.com/~kernel-ppa/mainline/ or is it http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please advise.

Second, the directions say I need to uninstall proprietary or out-of-tree modules (ex. vitualbox, nvidia, fglrx, bcmwl, etc.) [unless there is an extra package available for the version I am testing]. How can I tell what's installed?

Otherwise I think I can follow the directions on the MainlineBuilds page.

Thank you very much.

[mash (mash-econs)]

Is it possible that I have a bad or incomplete install of 3.19.0-29? Is there a verify or reinstall option in aptitude that might help?

[Max Waterman (b-ubuntuone)]

I see exactly the same thing - I only upgraded on Friday (11-9-2015). To successfully boot I manually select the previous kernel (-28) and then I can enter a password.

Surely there are tests for this use-case?

I'm using a Lenovo X250.

[romain (azurant)]

Hi,

I have similar problem with lenovo T450S.

lubuntu 3.19.0-29, it is impossible to tape the passphrase but I could tape my passphrase and decrypt when I reboot on 3.19.0-28.

Romain

[Zubair Khan (zkhan)]

I have discovered that while I thought I was affected by this bug, it is in fact this one:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689

Fix mentioned in #49 on that thread worked around the issue for me.

[mash (mash-econs)]

the problem persists. Can I get a sense of how this is going? Thanks.

[penalvch (penalvch)]

mash, this has been pending the results of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/comments/4 .

[mash (mash-econs)]

Please see my response at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/comments/5 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/comments/6 I don't know enough to follow these instructions. I am willing to do the work with some additional guidance. Thank you very much.

[Adam Carter (dmcrtr)]

I ran into this as well on 3.19.0-30. I can confirm this is fixed on the upstream kernel as well as in Willy on the xps 9343

[mash (mash-econs)]

Apparently resolved on my upgrade to 15.10 today. Thank you, team.

[penalvch (penalvch)]

mash, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/comments/14 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.