Using a regular key for a multimedia function in gnome-keybinding-properties renders that key useless
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
control-center (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Example:
Open gnome-keybindin
Now try and type the letter b normally anywhere - it doesn't work.
Using xev, typing the letter b should normally give this response:
KeyPress event, serial 26, synthetic NO, window 0x3800001,
root 0x119, subw 0x0, time 523284114, (93,381), root:(96,430),
state 0x10, keycode 56 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b"
XmbLookupString gives 1 bytes: (62) "b"
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x3800001,
root 0x119, subw 0x0, time 523284214, (93,381), root:(96,430),
state 0x10, keycode 56 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b"
But after assigning that key combo above, we get:
KeyPress event, serial 30, synthetic NO, window 0x3800001,
root 0x119, subw 0x0, time 523335268, (470,619), root:(473,668),
state 0x10, keycode 56 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x3800001,
root 0x119, subw 0x0, time 523335368, (470,619), root:(473,668),
state 0x10, keycode 56 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
The key has to be reset using xmodmap:
$ xmodmap -e 'keycode 56 = b'
for normal function to return.
Obviously, none of this should happen. It's just too silly.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.