My experience after the first few minutes, where it was in flux,
sometimes operating as Caps_Lock and sometimes as BackSpace, was that it
settled down to acting as BackSpace (as configured) but would not
repeat—viz., holding backspace deleted many characters, while holding
caps lock deleted only one character.

I've found that using xmodmap to remap the caps lock key's keycode to
BackSpace works to make it repeat correctly.

For me, the Caps Lock key is keycode 66; I believe this may vary from
machine to machine. If that be so, you can find out what it is for you
with ``xev`` (run it, press the caps lock key, look for the keycode
part).

    xmodmap -e 'keycode 66 = BackSpace'

I believe that putting the "keycode 66 = BackSpace" line in ~/.Xmodmap
is supposed to fix it automatically on login; I don't know as I haven't
closed my session since applying this fix. If not, I guess it could go
somewhere else. (Something which would be executed at X startup time?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215826

Title:
  Lost ability to remap Caps Lock to Ctrl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to