Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1836047 +++
Created attachment 1688721[details]
Screenshot showing error message: 'us-altgr-intl' is not a valid keyboard layout and variant specification
Description of problem:
Installing Fedora 32 trough a kickstart file with keyboard layout 'us-algr-intl' results in
DBusError: 'us-altgr-intl' is not a valid keyboard layout and variant specification
Version-Release number of selected component (if applicable):
anaconda 32.24.7-1.fc32
How reproducible:
always
Steps to Reproduce:
0. Prepare a kickstart file with option 'keyboard --vckeymap=us-altgr-intl' or 'keyboard us-altgr-intl' and make it accessible at http://<some-http-server/fedora.ks
1. Boot using https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-32-1.6.iso
2. Once the Fedora 32 menu appears, move the cursor to 'Install Fedora 32'
3. Press Tab
4. Change line to 'vmlinuz initrd=initrd.img ks=http://<some-http-server/fedora.ks'
5. Press Enter
Alternatively:
0. Prepare a kickstart file with option 'keyboard --vckeymap=us-altgr-intl' or 'keyboard us-altgr-intl' and make it accessible at http://<some-http-server/fedora.ks
1. Boot through PXE/iPXE using the following iPXE script
#!ipxe
set base-url http://dl.fedoraproject.org/pub/fedora/linux/releases/32/Everything/x86_64/os/images/pxeboot/
kernel ${base-url}vmlinuz initrd=initrd.img ks=http://<some-http-server/fedora.ks
initrd ${base-url}initrd.img
Actual results:
Error message during installation:
dasbus.error.DBusError: 'us-altgr-intl' is not a valid keyboard layout and variant specification
Expected results:
Working installation of Fedora 32 with keyboard layout 'us-altgr-intl'
Additional info:
This worked fine up until and including Fedora 31. 'us-algr-intl' should be a valid vckeymap parameter according to https://docs.fedoraproject.org/en-US/fedora/f32/install-guide/appendixes/Kickstart_Syntax_Reference/#sect-kickstart-commands-keyboard since
# find /usr/lib/kbd/keymaps/ -name us-altgr-intl*
/usr/lib/kbd/keymaps/xkb/us-altgr-intl.map.gz
Once Fedora 32 is installed (using a different keyboard layout) the layout can be changed to 'us-altgr-intl' through:
# localectl set-keymap us-altgr-intl
# localectl status
System Locale: LANG=en_US.UTF-8
VC Keymap: us-altgr-intl
X11 Layout: us
X11 Variant: euro
RHEL-8.3.0-20200602.n.1
RHEL crash at the beginning of the installation:
Starting installer, one moment...
anaconda 33.16.3.4-1.el8 for Red Hat Enterprise Linux 8.3 (pre-release) started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
* if the graphical installation interface fails to start, try again with the
inst.text bootoption to start text installation
* when reporting a bug add logs from /tmp as separate text/plain attachments
Traceback (most recent call last):
File "/sbin/anaconda", line 497, in <module>
keyboard.activate_keyboard(localization_proxy)
File "/usr/lib64/python3.6/site-packages/pyanaconda/keyboard.py", line 140, in activate_keyboard
sync_run_task(task_proxy)
File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task
task_proxy.Finish()
File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 447, in _call_method
**kwargs,
File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 476, in _get_method_reply
return self._handle_method_error(error)
File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 498, in _handle_method_error
raise exception from None
dasbus.error.DBusError: 'us-altgr-intl' is not a valid keyboard layout and variant specification
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 (anaconda 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:4729