Bug 731596 - .bashrc entry --- xmodmap -e "remove lock = Caps_Lock"-- no longer switches off Caps Lock key
Summary: .bashrc entry --- xmodmap -e "remove lock = Caps_Lock"-- no longer switches o...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server-utils
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-17 23:32 UTC by rene reitsma
Modified: 2018-04-11 08:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-22 13:52:11 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description rene reitsma 2011-08-17 23:32:19 UTC 
Description of problem:

The .bashrc entry:

xmodmap -e "remove lock = Caps_Lock"

no longer (after upgrading from fc13 to fc15) switches off the Caps Lock key.

Version-Release number of selected component (if applicable):
bash --version
GNU bash, version 4.2.10(1)-release (i386-redhat-linux-gnu)

How reproducible: always

Steps to Reproduce: 
1. stick the line in .bashrc
2. source .bashrc
3. toggle the Caps Lock key (should no longer toggle, but does)
  
Actual results: Caps Lock not switched off

Expected results: Caps Lock switched off


Additional info:
Comment 1 Roman Rakus 2011-08-18 12:57:52 UTC 
I don't see any relation to bash. Changing component to xorg-x11-server-utils
Comment 2 Matěj Cepl 2011-08-22 13:52:11 UTC 
I believe that the correct sanctioned way is

xmodmap -e 'clear Lock'

(mentioned in the manpage).

Unless it is broken for you, I stand behind this bug being a configuration issue.
Comment 3 rene reitsma 2011-08-22 17:12:31 UTC 
Neither 

xmodmap -e "remove lock = Caps_Lock"

nor

xmodmap -e 'clear Lock'

nor 

xmodmap -e "clear Lock"


seem to work; Caps Lock remains active (toggling) in all cases.

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