Bug 476106
| Summary: | Control key with multiple keyboards does not work with evdev | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sam Creasey <sammy> | ||||||||
| Component: | xorg-x11-drv-evdev | Assignee: | Peter Hutterer <peter.hutterer> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 10 | CC: | xgl-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-10-08 06:52:35 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Sam Creasey
2008-12-11 23:43:04 UTC
I just tried this on my F10 installation and it worked fine. Please attach the xev output when you hold ctrl on one keyboard and press keys on the other. attaching two xev dumps. They are, afaict, identical. The first dump (same keyboard), consists of switching from the xev window to a terminal window, executing a ctrl-a followed by a ctrl-e. (expected behavios was observed -- cursor went to the beginning of the line and back to the end). The second attachement (diff keyboard) is basically indistunguishable from the xev output, however, the behavior was: switch from xev window to terminal window. Hold ctrl key and press 'a'. Watch 'a' get printed on command line. press 'a' again with pedal held, and go to beginning of line. release ctrl. press ctrl, hold and press 'e'. Watch 'e' get printed. while ctrl is still held, press 'e' again, and watch cursor move to end of line. Created attachment 327613 [details]
same keyboard
Created attachment 327614 [details]
diff keyboard
if you switch away from xev, it won't receive the events anymore. Please leave the xev window focused, and hit ctrl + a in all four combinations (kbd1 + kbd1, kbd1 + kbd2, kbd2+kbd1, kbd2+kbd2). Created attachment 327638 [details]
xevent dump with window focuses
only had pedals+keyboard connected, so the key sequence is...
hold ctrl on kbd1, press 'a' on kbd1, release all keys
hold ctrl on kbd2, press 'a' on kbd1, while ctrl is held, press 'a' again, release all kets
hold ctrl on kbd1, press 'e' on kbd1, release all keys
hold ctrl on kbd2, press 'e' on kbd1, while ctrl is held, press 'e' again.
wait, I just noticed that "The problem occurs with many different keycodes mapped to "control" in xmodmap." If you do not have anything in your xmodmap, do the normal control keys work fine? with no changes to xmodmap, the problem occurs. I only brought xmodmap into the picture to make sure the issue was due to keys being mapped to "control", rather than the actual scancode of the left control key. weird, I just tested it on another F10 box and it works as well. what's the output of setxkbmap -print? [pts/6]sammyville:~% setxkbmap -print
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us" };
xkb_geometry { include "pc(pc101)" };
};
sorry, previous comment was with kbd driver. evdev has:
[pts/0]sammyville:~% setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc104)" };
};
This feature was disabled in server 1.6 (Fedora 11) in the X server. It got re-enabled with server 1.7 and is available again in the upcoming F12. Since F10 will be retired soon and due to the huge number of changes to the input system this bug won't be fixed in F10. F11 - as I said, it was an intentional upstream design (though a tad misguided). Closing as NEXTRELEASE, this feature is back in F12. |