with multiple keyboard layouts and caps-lock remapped, control_l is both control and lock

Bug #231800 reported by David Carlton
2
Affects Status Importance Assigned to Milestone
xkeyboard-config (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I have two keyboard layouts configured (USA/Dvorak and USA/Standard), and I have Caps Lock set to a second Control key. When I upgraded to 8.04, I noticed Emacs behaving somewhat oddly; the most concrete manifestation of this is that, if I start up XEmacs and hit the space bar, I get messages like "(3) (key-mapping/warning) XEmacs: Caps_Lock (0x42) generates ModControl, which is nonsensical. (4) (key-mapping/warning) XEmacs: Control_L (0x42) generates ModLock, which is nonsensical."

Doing 'xmodmap -pm', I see, among other things:

lock Control_L (0x42)
control Control_L (0x25), Control_L (0x42), Control_R (0x6d)

So Control_L is indeed mapped to two different modifiers.

If I remove one of the keyboard layouts, the entry in the 'lock' row disappears.

At first, I thought this was Bug 173350 (which I'm also seeing), but it isn't: I get the Caps Lock light toggling state even if I only have a single keyboard layout, whereas the behavior in this bug depends on having multiple keyboard layouts.

I'm using Ubuntu 8.04, x86_64. This didn't happen with previous Ubuntu versions.

Tags: hardy
Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach your /var/log/Xorg.0.log

Changed in xorg-server:
status: New → Incomplete
Revision history for this message
David Carlton (carlton-bactrian) wrote :

Here you go.

Revision history for this message
David Carlton (carlton-bactrian) wrote :

I happened to look at this bug again, and I saw the expiry warning, because the bug is marked as Incomplete; is there any information that I need to provide, or is it incomplete for reasons unrelated to my actions? It's still happening, and is still annoying. (Only mildly so, but in general the keyboard behavior on 8.04 is the main reason why I haven't upgraded my other machine off of 7.10.)

Bryce Harrington (bryce)
Changed in xkeyboard-config:
importance: Undecided → Medium
status: Incomplete → Triaged
Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi David, are you still able to reproduce this issue still on a recent version of Ubuntu? I'm not sure how exactly this could be fixed, but perhaps we could forward the bug upstream if it still occurs.

I don't think any additional data is needed, although you could run 'apport-collect 231800', which will attach keyboard configuration files and so on.

Changed in xkeyboard-config (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
David Carlton (carlton-bactrian) wrote :

Unfortunately, the computer in question died last year, and my current Ubuntu machine is a remote machine that I ssh into, so I can't confirm whether or not the bug is still present.

Revision history for this message
Bryce Harrington (bryce) wrote :

Since the hardware is no longer available for doing troubleshooting with, we'll have to close the bug for now. However please feel free to reopen if you or anyone else has the same HW and can reproduce this issue using the latest development version of Ubuntu and is willing to do some troubleshooting with it.

Changed in xkeyboard-config (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.