[CAPSLOCK] shift-control ignored after re-mapping CAPSLOCK and Control

[pauljohn32]

Binary package hint: xmodmap

I followed the xmodmap man page to swap the CAPSLOCK and Control keys. That part works great.

However, after re-mapping, other key combinations with the Control key (which is the one labeled CAPS) do not work. Shift-Control-s in the Gimp is supposed to cause "save as", but nothing happens. Since key combinations are very important in Emacs, this is a pretty big problem for me.

[mmomjian (matthew-momjian)]

can you post the actual xmodmap command you used? thanks.

[pauljohn32 (pauljohn)]

Yes, I realized I should have posted the actual xmodmap file. AFAIK, this is exactly same as man page

remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L

[Friedrich Strohmaier (bitsfritz)]

@pauljohn32: I've setup bug #512622 which in general matters strange xmodmap keymapping.
If You think this affects You, or maybe could solve Your Problem then please strike the apropriate handle ;o))

Maybe many keybord related problems can be solved that way.

[pauljohn32 (pauljohn32)]

I'm sorry, Friedrich. I cannot understand your words. If you mean that Ubuntu has fixed the problem, I do not agree. On my system, using the xmodmap file I gave above, the key combinations like Shift-Control-S don't do anything.

[Friedrich Strohmaier (bitsfritz)]

I setup a bugreport which is collecting bugs which aparently relate to xmodmap problems. Many of those only affect *one* person. I try to get more "votes" to get things in motion. And no: that doesn't mean I think the bug is fixed - in contrary!

Did you read description of bug #512622 ? Can You confirm what I described there? If yes, please hit the "This b ug affects me" button on top. If we are lucky (and busy) more people vote and tell the developers: This Bug is important! Please Fix! ;o))

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi pauljohn32,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 307008

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 307008 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/307008

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.