Bug 174395
Summary: | KeyPress order matters when changing workspaces using Shift+Meta_L+[arrows] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> |
Component: | xorg-x11-xkbdata | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | jturner |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 10:29:40 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: |
Description
James Laska
2005-11-28 19:33:42 UTC
Further investigation reveals that the keycode is different when I use a different keypress order. For example: - Pressing "Meta_L+Shift+Left" shows up in `xev` as Alt_L, Shift_L - Pressing "Shift+Meta_L+Left" shows up in `xev` as Shift_L, Meta_L Is this a changed behavior from before? I didn't think that shift would act as a modifier for the alt key? Perhaps it would be helpful to look at my `xmodmap` xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 mod4 Super_L (0x7f), Hyper_L (0x80), Super_L (0x73) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c) Sure enough, using gnome-keybinding-properties, changing the order of the key press (swapping order of Shift and Alt keys) changes what keys it thinks were pressed. I just tested the keypress ordering on a Red Hat Enterprise Linux 4 Update 2 system and it appears to not care which order I hit Alt and Shift in. Please report this issue to X.Org developers by filing a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "NEEDINFO_REPORTER", awaiting X.Org bug URL for tracking. FC5test3 has now been released, which might resolve this issue. Please update to FC5test3, and if the problem persists, file a bug report in the X.Org bugzilla at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "RAWHIDE". |