FS#63579 - [kbd] keyboard not working on reboot (induces: unable to enter luks password)

Attached to Project: Arch Linux
Opened by Max Ruman (rmx) - Wednesday, 28 August 2019, 05:56 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 28 August 2019, 05:59 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After a system upgrade that installed the latest `testing/kbd` (2.2.0-2) and after having rebooted, I couldn't enter anymore my LUKS password on boot. The ENTER key didn't work (couldn't test other keys, because the password input is shadowed), except ALT that seemed to worked like ENTER. CTRL-ALT-DELETE had no effect.

I chrooted with a rescue USB, tried different things in mkinitcpio.conf, reinstalled the kernel and systemd, finally found that the `kbd` package was installed during the last upgrade. Reverting to `core/kbd` (2.0.4-2) fixed the issue. I added `kbd` to the IgnorePkg list to prevent upgrading.

The package was very recently released as 2.2.0-4, and I suggest to remove this release before an investigation was done, as it may potentially break the boot of all the people who have enabled the pacman testing packages and made an upgrade.


Additional info:
* package version: kbd 2.2.0-2 (latest testing/kbd)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
* having encrypted partitions with luks
* install latest testing/kbd (2.2.0-2)
* ensure mkinitcpio has run
* reboot
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 28 August 2019, 05:59 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#63565 

Loading...