Bug 1200951 - Dracut v57 update breaks (at least) loading of keymaps during boot
Summary: Dracut v57 update breaks (at least) loading of keymaps during boot
Status: RESOLVED DUPLICATE of bug 1200950
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: Other openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-26 21:11 UTC by Hadrien Grasland
Modified: 2022-06-27 07:54 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hadrien Grasland 2022-06-26 21:11:39 UTC
After updating to the latest tumbleweed snapshot, the boot prompt used to decrypt my LUKS root partition has switched to QWERTY, which is not my normal keyboard layout and thus makes it harder to type the password.

The following log in journalctl seems like the most likely explanation...

juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[682]: cannot open include file azerty-layout
juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[682]: syntax error, unexpected ERROR
juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[680]: /usr/bin/loadkeys failed with exit status 1.

...and indeed, if I rollback to the previous snapper snapshot and install everything but the dracut update (this still includes a minor kernel update and thus an initrd rebuild), everything is fine. So clearly the dracut update is somehow involved in this.

It looks like somehow, after the dracut update, the initrd does not feature the azerty-layout keymap anymore. There might be more initrd breakage that I cannot see.
Comment 1 Ingo Göppert 2022-06-27 05:24:48 UTC
Same error with the de-latin1 layout on my system.
Comment 2 Jiri Slaby 2022-06-27 07:54:15 UTC
.

*** This bug has been marked as a duplicate of bug 1200950 ***