Bug 1951459 - Removal of the xorg symlinks broke keymap handling
Summary: Removal of the xorg symlinks broke keymap handling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xkeyboard-config
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1950406 1951875
TreeView+ depends on / blocked
 
Reported: 2021-04-20 07:46 UTC by Peter Hutterer
Modified: 2021-05-06 01:00 UTC (History)
8 users (show)

Fixed In Version: xkeyboard-config-2.32-3.fc34
Clone Of:
Environment:
Last Closed: 2021-05-06 01:00:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Hutterer 2021-04-20 07:46:46 UTC 
Description of problem:
See Bug 1950406 for details but the summary is that console-setup still used the `xorg` symlinks for the rules{.lst|.xml|} files so when that disappeared, it didn't generate the right keymaps anymore.

At least for Fedora 34, we should just restore the old symlinks.

Additional info:
Bug 1951453 has been filed for console-setup
Comment 1 Fedora Update System 2021-04-20 08:06:53 UTC 
FEDORA-2021-13846a3738 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-13846a3738
Comment 2 Fedora Update System 2021-04-20 22:25:39 UTC 
FEDORA-2021-13846a3738 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-13846a3738`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-13846a3738

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2021-05-06 01:00:27 UTC 
FEDORA-2021-13846a3738 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.