FS#23272 - [xkeyboard-config] [xorg-xmodmap] are conflicting in some manner
Attached to Project:
Arch Linux
Opened by Drew (r4) - Monday, 14 March 2011, 19:04 GMT
Last edited by Jan de Groot (JGC) - Monday, 11 April 2011, 07:07 GMT
Opened by Drew (r4) - Monday, 14 March 2011, 19:04 GMT
Last edited by Jan de Groot (JGC) - Monday, 11 April 2011, 07:07 GMT
|
Details
Description:
xkeyboard-config 2.1-1 and xorg-xmodmap 1.0.5-2 are conflicting in some manner. Essentially what is happening, whenever I try to remap a key with xmodmap, xkeyboard-config is preventing the key remap from taking place. I checked 'xmodmap' in terminal and according to xmodmap, the remap is taking place. However, I was unable to get the remap to work until i downgraded the xkeyboard-config package. There were no errors when trying to actually remap the key with xmodmap (other than it not working) and Xorg.0.log showed no errors. It is very unclear as to why this might be happening. Additional info: xkeyboard-config 2.1-1 xorg-xmodmap 1.0.5-2 Steps to reproduce: 1. Install most recent packages of xkeyboard-config and xorg-xmodmap 2. xmodmap -e "remove Lock = Caps_Lock" xmodmap -e "clear Mod3" xmodmap -e "add Mod3 = Caps_Lock" |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 11 April 2011, 07:07 GMT
Reason for closing: Not a bug
Additional comments about closing: See upstream bug.
Monday, 11 April 2011, 07:07 GMT
Reason for closing: Not a bug
Additional comments about closing: See upstream bug.
It's about halfway down the post on comment 14.
This is the fix.
I want my <CAPS> key to be bound to Mod3 modifier:
xmodmap -e 'remove lock = Caps_Lock' -e 'keysym Caps_Lock = ISO_Level5_Shift'
-e 'add mod3 = ISO_Level5_Shift'
(note that I used ISO_Level5_Shift as a keysym, which is generally used
together with mod3. But it doesn't really matter: just don't use Caps_Lock or
else you will have your lock back)