https://bugzilla.redhat.com/show_bug.cgi?id=1405539
--- Comment #29 from Ray Strode [halfline] <rstrode(a)redhat.com> ---
My opinion is that is hard enough to fix that it's unlikely to get traction
this release.
To do it right, we need an indicator in plymouth. We'd have to start with
adding a kernel api for querying the console keymap. We don't currently show
fonts in the initramfs, so the indicator would have to be image based. And at
the moment, switching console keymaps requires knowing a keymap specific key
combination, which isn't shared with X. So having the indicator still leaves
the user somewhat trapped, if they don't know the combo.
We could make it plymouth use /dev/input instead of the console, but that would
require extensive changes to the code base.
Rebuilding the initramfs from systemd or control-center doesn't really solve
anything. User may still reboot weeks after changing it and not realize the
change affects boot screen.
Not changing the keymap for single user case sucks for that user too, unless we
started using autologin for single users, so they don't see the login screen,
but that's a big change, and doesn't help precisely in the case of encrypted
disk.
Also, the person who was going to dive into this switched teams and doesn't
work on plymouth anymore.
I think the behavior we have now is suboptimal, but we've had it ~forever, and
fixing it is hard enough, that I don't see how this could be a blocker,
personally.
--
You are receiving this mail because:
You are on the CC list for the bug.