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 2139165 - jp106 keymap does not exist in /lib/kbd/keymaps but is used in /etc/vconsole.conf anyway
Summary: jp106 keymap does not exist in /lib/kbd/keymaps but is used in /etc/vconsole....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kbd
Version: 9.1
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Vitezslav Crhonek
QA Contact: Evgeny Fedin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-01 16:56 UTC by Aakhil Kassim
Modified: 2023-11-07 11:36 UTC (History)
1 user (show)

Fixed In Version: kbd-2.4.0-9.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:55:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-138000 0 None None None 2022-11-01 17:00:55 UTC
Red Hat Product Errata RHBA-2023:6673 0 None None None 2023-11-07 08:55:31 UTC

Description Aakhil Kassim 2022-11-01 16:56:23 UTC 
Description of problem:
Selecting the "Japanese" as the primary keyboard layout during installation results in the virtual console falling back to standard keyboard layout instead of the Japanese layout after installation. X or Wayland seem to be working OK though.

Version-Release number of selected component (if applicable):
This applies to RHEL 9.0 and RHEL 9.1 Beta as of November 1 2022.

Reproducibility:
Happens any time you install RHEL 9.1 with Japanese as primary keyboard layout.

Actual results:
Investigating in localectl and /etc/vconsole.conf shows that KEYMAP="jp106". However, there is no jp106.map.gz file in the /lib/kbd/keymaps directory. It is worth mentioning there is a file called jp.map.gz and it works good if you set vconsole to use it instead of jp106.
Searching in journalctl also reveals the errors:
Nov 01 12:09:37 kashew systemd-vconsole-setup[252]: loadkeys: Unable to open file: jp106: No such file or directory
Nov 01 12:09:37 kashew systemd-vconsole-setup[248]: /usr/bin/loadkeys failed with exit status 1.

Expected results:
Post installation, the keyboard layout chosen as default in Anaconda should function without error in the virtual console.

Some workarounds:
Set KEYMAP to just "jp" in /etc/vconsole.conf
OR Copy /lib/kbd/keymaps/jp.map.gz to /lib/kbd/keymaps/jp106.map.gz and reboot
OR just run loadkeys jp each time you want the Japan layout to work since that file exists.

Thanks have a wonderful day :)
Comment 1 Vitezslav Crhonek 2022-11-02 08:26:35 UTC 
Hello Aakhil,

Thank you for the bug report.

jp106.map.gz is part of kbd-legacy package, do you have it installed?

# rpm -ql kbd-legacy | grep jp
/usr/lib/kbd/keymaps/legacy/i386/qwerty/jp106.map.gz

If not, installing kbd-legacy package is the solution. But it should be
installed automatically as the kbd package requirement. It is still optional
in RHEL9 and it can cause this problem for some languages.

(If you're interested in more detail, see Fedora bug #2127513.)
Comment 2 Aakhil Kassim 2022-11-02 13:36:40 UTC 
(In reply to Vitezslav Crhonek from comment #1)
> Hello Aakhil,
> 
> Thank you for the bug report.
> 
> jp106.map.gz is part of kbd-legacy package, do you have it installed?
> 
> # rpm -ql kbd-legacy | grep jp
> /usr/lib/kbd/keymaps/legacy/i386/qwerty/jp106.map.gz
> 
> If not, installing kbd-legacy package is the solution. But it should be
> installed automatically as the kbd package requirement. It is still optional
> in RHEL9 and it can cause this problem for some languages.
> 
> (If you're interested in more detail, see Fedora bug #2127513.)

Hi Vitezslav,

I wasn't aware there was an optional legacy package for kbd.
It is nice to see it is getting taken care of in Fedora 37.

What is the likelihood it could be backported to RHEL9?
As that would provide some extra convenience.

Thank you for clarifying this. Take care.
Comment 3 Vitezslav Crhonek 2022-11-03 10:59:22 UTC 
(In reply to Aakhil Kassim from comment #2)
> 
> What is the likelihood it could be backported to RHEL9?
> As that would provide some extra convenience.
> 

I agree, we should fix this in RHEL9.
I plan the update in RHEL9.3 timeframe for now.
Comment 12 errata-xmlrpc 2023-11-07 08:55:30 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 (kbd 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-2023:6673
Note You need to log in before you can comment on or make changes to this bug.