Bug 2214130

Summary: Unable to set keymap to "gb" on minimal install
Product: Red Hat Enterprise Linux 9 Reporter: Vikramsingh Patil <vikpatil>
Component: systemdAssignee: systemd maint <systemd-maint>
Status: CLOSED MIGRATED QA Contact: Frantisek Sumsal <fsumsal>
Severity: low Docs Contact: Šárka Jana <sjanderk>
Priority: low    
Version: 9.0CC: eng-i18n-bugs, fkrska, gfialova, gspencer, jwright, sbarcomb, sjanderk, systemd-maint-list
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Setting the console `keymap` requires the `libxkbcommon` library on your minimal install In RHEL 9, certain `systemd` library dependencies have been converted from dynamic linking to dynamic loading, so that your system opens and uses the libraries at runtime when they are available. With this change, a functionality that depends on such libraries is not available unless you install the necessary library. This also affects setting the keyboard layout on systems with a minimal install. As a result, the `localectl --no-convert set-x11-keymap gb` command fails. To work around this problem, install the `libxkbcommon` library: ---- # dnf install libxkbcommon ----
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 15:15:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vikramsingh Patil 2023-06-12 03:32:51 UTC
Description of problem:
Unable to set keymap to "gb" on minimal install

Version-Release number of selected component (if applicable):
ibus-1.5.25-2.el9

How reproducible:

- on RHEL 9 minimal install. Reproduceable on 9.0, 9.1 and 9.2

Steps to Reproduce:

Run "localectl --no-convert set-x11-keymap gb"

Actual results:

Failed to set keymap: Local keyboard configuration not supported on this system.

Expected results:

keymap changed successfully

Additional info:

Comment 2 Parag Nemade 2023-06-12 03:40:21 UTC
Well, its not clear here which language you want to set. is it British English? if yes then you should say unable to set "en_GB" keymap.
GB is neither locale nor language.

Comment 4 gspencer 2023-06-12 11:12:31 UTC
I have attempted that:-

localectl --no-convert set-x11-keymap en_GB
Failed to set keymap: Local keyboard configuration not supported on this system.

and specifying en-GB also fails on this system, just specifying "gb" has worked on all previous RHEL releases to date, EL6 / 7 / 8.

Comment 5 fujiwara 2023-06-12 11:31:51 UTC
I don't know why you reported your issue to ibus.

You cannot reproduce your issue when ibus-daemon does not run?
You can stop ibus-daemon with `ibus exit` command or im-chooser.

Comment 6 gspencer 2023-06-13 15:08:06 UTC
also please refer to:-
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/assembly_changing-basic-environment-settings_configuring-basic-system-settings

"section: 1.3. Configuring the keyboard layout"

prescribes configuring keymaps with just the two letters, as I have always done with my previous EL5/6/7/8 installs.

Comment 7 gspencer 2023-06-13 15:13:09 UTC
"I don't know why you reported your issue to ibus."   -   I didn't log the ticket so I'll leave that for RedHat tech support to answer/progress.

Comment 8 fujiwara 2023-06-14 03:07:51 UTC
(In reply to fujiwara from comment #5)
> You cannot reproduce your issue when ibus-daemon does not run?
> You can stop ibus-daemon with `ibus exit` command or im-chooser.

Please provide the exact information if you wish to report your issue to ibus.

Comment 10 Peter Hutterer 2023-06-15 01:00:18 UTC
> localectl --no-convert set-x11-keymap gb

Note that this sets the *X11* keymap, i.e. the one used by the X server. This is rather unusual on a minimal system, I would expect a call to `localectl set-keymap` instead to set the keymap used on the console. Is that what you meant to do?

Anyway, `dnf install libxkbcommon` should fix this issue. Note: libxkbcommon is in AppStream so that repository may need to get explicitly enabled if you're on a minimal install.

Comment 11 gspencer 2023-06-15 08:18:23 UTC
in addition to settiing the console keymap, I normally also set the x11 keymap the same, and there appears to have been a change in behaviour introduced with EL9, whereas this worked satisfactorily in EL5/6/7/8.  I haven't seen this change in behaviour documented anywhere, not the release notes or anything, so this change is unexpected.

Because while most of our servers are satisfied with a minimal install and just adding the necesssary server items, occasionally we will follow up with installation of a GUI, for example with subsequent install of Oracle.

It looks wrong for a localectl to return a foreign language setting for X11 and the local language setting for console, even if X11 is not used at that stage.

I'm just expecting EL9 to behave the same way as previous releases, unless there is a specific (documented) reason for it not to.

Comment 12 gspencer 2023-06-15 08:22:06 UTC
I can confirm 'dnf install libxkbcommon' resolves the issue, but why is it not in the release notes?

Comment 16 RHEL Program Management 2023-09-21 13:54:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 17 RHEL Program Management 2023-09-21 15:15:18 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.