Bug 707444 - Manipulation of Caps Lock modifier with xmodmap doesn't work in F15
Summary: Manipulation of Caps Lock modifier with xmodmap doesn't work in F15
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:conf_input]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 05:36 UTC by Tore Anderson
Modified: 2018-04-11 11:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log (62.36 KB, text/plain)
2011-05-28 07:55 UTC, Tore Anderson
no flags Details
00-system-setup-keyboard.conf (316 bytes, text/plain)
2011-05-28 07:59 UTC, Tore Anderson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 19795 0 None None None Never
FreeDesktop.org 31436 0 None None None Never
Launchpad 777882 0 None None None Never
Launchpad 785938 0 None None None Never

Description Tore Anderson 2011-05-25 05:36:50 UTC
Description of problem:

For ages my ~/.Xmodmap file has been used to:

1) clear the "lock" and "control" modifiers
2) add the "control" modifier to the Caps Lock button
3) add the "mod4" modifier to the Control button

However, this stopped working after upgrading to F15. The Caps Lock key still toggles the actual Caps Lock function, and does *not* at the same perform the Control function.

However, the clearing of the "control" modifier as well as the adding of the "mod4" modifier to the Control button still works. So I am essentially left without any key I can use to invoke the actual Control function.

Curiously enough, the output of "xmodmap" indicates that the remappings were successful. However, pressing the button does unfortunately not yield the desired results.

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

xorg-x11-server-Xorg-1.10.1-14.fc15.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Ensure the Caps Lock function is not active.
2. Run the command "echo remove Lock = Caps_Lock | xmodmap -"
3. Press the Caps Lock button.
4. Type some text into an application.
  
Actual results:

The input text is uppercase, and the Caps Lock indicator on my keyboard is lit.

Expected results:

The input text should have been lowercase, and the Caps Lock indicator should have remained unlit. In essence, pressing the Caps Lock button should have been a no-op.

Additional info:

Here's my .Xmodmap file (it has worked for ages):

$ cat .Xmodmap
remove Lock = Caps_Lock
remove Control = Control_L
remove Control = Control_R
add Mod4 = Control_L
add Control = Caps_Lock

This is the output of "xmodmap" after the .Xmodmap file has been loaded. Note how the lock modifier has no assigned buttons, while the Caps Lock key is assigned to the control modification (this is as expected, but the actual buttons behave differently):

$ xmodmap 
xmodmap:  up to 5 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock      
control     Caps_Lock (0x42)
mod1        Alt_L (0x40),  Meta_L (0xcd)
mod2        Num_Lock (0x4d)
mod3      
mod4        Control_L (0x25),  Super_L (0x85),  Super_R (0x86),  Super_L (0xce),  Hyper_L (0xcf)
mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

Comment 1 Tore Anderson 2011-05-25 05:42:01 UTC
This is very likely an upstream bug - Ubuntu users are seeing it too:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/777882
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/785938

Comment 2 Matěj Cepl 2011-05-28 00:05:36 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach

* your X server config file (/etc/X11/xorg.conf, if available), and
* X server log file (/var/log/Xorg.*.log)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 Matěj Cepl 2011-05-28 00:10:52 UTC
Not sure whether these two upstream bugs are related, but may add some food for thoughts.

Comment 5 Matěj Cepl 2011-05-28 00:13:11 UTC
Sorry, last comment: reporter are you able (as a workaround) to achieve the same result by the settings in your DE (Gnome, KDE and I believe XFCE should be able to do it)?

Thank you

Comment 6 Tore Anderson 2011-05-28 07:55:53 UTC
Created attachment 501450 [details]
Xorg.0.log

Comment 7 Tore Anderson 2011-05-28 07:59:18 UTC
(In reply to comment #2)

> Please attach
> 
> * your X server config file (/etc/X11/xorg.conf, if available), and

I do not have this file on my system. However, I do have a /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf - will attach in a second.

> * X server log file (/var/log/Xorg.*.log)

Attached.

(In reply to comment #5)

> Sorry, last comment: reporter are you able (as a workaround) to achieve the
> same result by the settings in your DE (Gnome, KDE and I believe XFCE should be
> able to do it)?

To the best of my knowledge, there's no keyboard remapping functionality built into the window manager I'm using (Openbox). So I don't think so, no.

Tore

Comment 8 Tore Anderson 2011-05-28 07:59:45 UTC
Created attachment 501452 [details]
00-system-setup-keyboard.conf

Comment 9 Tore Anderson 2011-05-28 10:47:36 UTC
I've found a workaround that allows me to disable the Caps_Lock key and turn it into a Control key - basically I have to *both* clear the modifier, and change the keysymname of they key to something else than Caps_Lock. Then I can add it to the control modifier:

$ cat .Xmodmap
clear lock
keycode 66 = Control_L
add control = Control_L

Tore

Comment 10 Alastair Scobie 2012-04-13 09:46:30 UTC
We are experiencing the same problem under RHEL6.2 with 

xorg-x11-server-Xorg-1.10.4-6.el6

Comment 11 Fedora End Of Life 2012-08-06 19:59:58 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 12 Fedora End Of Life 2012-08-06 20:00:42 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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