Bug 1399853 - xmodmap and setxkbmap no longer works correctly on Fedora 25
Summary: xmodmap and setxkbmap no longer works correctly on Fedora 25
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 22:20 UTC by Jordan Sissel
Modified: 2017-12-12 10:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:09:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jordan Sissel 2016-11-29 22:20:01 UTC
Description of problem:

I use xmodmap to change key  mappings. On Fedora 24, this used to work. On FEdora 25, this no longer works.

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


How reproducible: Always


Steps to Reproduce:

Example 1: Changing capslock:

xmodmap -e "remove Lock = Caps_Lock"
xmodmap -e "remove Lock = Control_L"
xmodmap -e "keycode 66 = Control_L Control_R"
xmodmap -e "add Control = Control_R Control_R"

Example 2: Changing F1 to be Escape

xmodmap -e 'keycode 67 = Escape'

Actual results:

capslock: xmodmap is completes, but the capslock key still behaves like normal caps lock (making letters capitalized, acting as a toggle/lock)

f1: F1 key still behaves as F1 (opens 'help' in many apps instead of acting like an escape key)

Expected results:

capslock: key mapping should take effect. In the example above, the caps lock key should act as a control key.

f1: F1 key should act as escape.


Additional info:

Running the `xev` program, it shows the keysyms are correct, so the X11-side of things is working, but Wayland is not aware, maybe?

Sample xev output:

Pressing F1:
    state 0x0, keycode 67 (keysym 0xff1b, Escape), same_screen YES,

Pressing caps (mapped to control):
    state 0x2, keycode 66 (keysym 0xffe3, Control_L), same_screen YES,

Comment 1 Gavin Burris 2017-02-16 16:44:50 UTC
I have had to set the options with X/Wayland and Gnome, because Gnome ignores it otherwise:
$ setxkbmap -layout us -option caps:ctrl_modifier
$ gsettings set org.gnome.desktop.input-sources xkb-options "['caps:ctrl_modifier']"

Comment 2 Fedora End Of Life 2017-11-16 19:51:11 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:09:18 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.