RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1688935 - LUKS boot password prompt keyboard layout
Summary: LUKS boot password prompt keyboard layout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: plymouth
Version: 8.2
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: 8.0
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1681715
Blocks: 1825061 1880509 1907422
TreeView+ depends on / blocked
 
Reported: 2019-03-14 18:08 UTC by Jakub Bittner
Modified: 2020-12-14 13:49 UTC (History)
8 users (show)

Fixed In Version: plymouth-0.9.4-1.20200615git1e36e30.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1880509 (view as bug list)
Environment:
Last Closed: 2020-11-04 04:04:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4810 0 None None None 2020-11-04 04:04:18 UTC

Description Jakub Bittner 2019-03-14 18:08:14 UTC 
Description of problem:
LUKS graphical password prompt during boot does not tell user keyboard layout.

Version-Release number of selected component (if applicable):


How reproducible:
Boot system with LUKS encrypted volume.

Steps to Reproduce:
1. Install RHEL with encrypted (root) volume
2. Reboot
3. Wait till LUKS password prompt appears
4. Look around for keyboard layout icon/text

Actual results:
No way to find out what keyboard layout is used for input

Expected results:
User knows input keyboard layout

Additional info:
In case you installed RHEL with default (English) keyboard layout, you will not notice any problem. In case RHEL uses different layout than english, user is not able to find which one and password input may be a problem.
Comment 2 Hans de Goede 2019-08-04 08:26:11 UTC 
Note Alberto Ruiz and I have been looking into doing a keyboard-layout indicator for plymouth for Fedora. There is a UI design for how this should look like (for Fedora) here: https://gitlab.gnome.org/Teams/Design/os-mockups/raw/master/password-entry/password-entry.png and then specifically the "Disk Encryption" mockups at the end.

This is something which we plan to work on sometime in the future. Support for this cannot be added to RHEL until support has been added for this to the upstream plymouth code.

Figuring out which keyboard layout is in use is going to be somewhat tricky. We will likely need to reproduce the kernel commandline and /etc/vconsole.conf parsing from systemd-vconsole-setup and assume that systemd-vconsole-setup has done its work properly.

If someone wants to work on this, please contact me or Alberto for coordination so that we do not do double work.
Comment 3 Hans de Goede 2019-10-12 10:57:37 UTC 
The changes implementing keyboard layout indicator have landed upstream and in Fedora 31, currently in Fedora this looks like this (with capslock active, so including capslock warning symbol):
https://fedorapeople.org/~jwrdegoede/flickerfree-videos/keyboard-indicators.png

This will likely require some work to adjust for the RHEL-8 plymouth theme.

Upstream plymouth has seen a lot of changes recently, so backporting this will be non trivial. A lot of those changes are also necessary to deal better with modern DisplayPort MST (multi stream transport) laptop-docks where external monitors may show up after plymouth has started, because DP MST enumeration is slow. For this reason upstream plymouth now supports monitor hot(un)plug, something which we really also need for RHEL. As such I believe that a rebase to the latest upstream version (after upstream has done a new release) would be the best solution to get this functionality into RHEL.
Comment 14 Tomas Pelka 2020-09-18 18:06:00 UTC 
OK after chat with halfline I was able to verify that the layout is showed properly.

Just note that you need to have plymouth-theme-spinner rpm installed.

Than you need to 
plymouth-set-default-theme  --rebuild-initrd bgrt
to set the default theme

After that I can see the layout.

Moving to verified.

The initrd rebuild is not done automatically therefore halfline created - Bug 1880509, let's see if we can still pull it to 8.3.
Comment 17 errata-xmlrpc 2020-11-04 04:04:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (plymouth bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4810
Note You need to log in before you can comment on or make changes to this bug.