After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703724 - XF86Tools keyboard button can't be used as shortcut key
XF86Tools keyboard button can't be used as shortcut key
Status: RESOLVED DUPLICATE of bug 781223
Product: gnome-shell
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-07-07 04:02 UTC by Tim Cuthbertson
Modified: 2017-05-31 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim Cuthbertson 2013-07-07 04:02:29 UTC
I have a MacAlley IceKey keyboard, which has F1-F15 function keys.

Using the gnome keyboard settings, I've bound F13, F14 and F15 to play/pause, previous and next track respectively. The keyboard settings app describes these keys as "Tools", "Launch5" and "Launch6".

The F14 and F15 bindings work, but the F13 binding ("Tools") does not. Binding it to a different action does not work, and binding a different key to the play/pause action does work - so it's clearly specific to this key.

using `xev`, I can see that pressing the key registers a reasonable-looking input event for "XF86Tools":

KeyPress event, serial 33, synthetic NO, window 0x1c00001,
    root 0x2bf, subw 0x0, time 3485114, (274,488), root:(1238,544),
    state 0x0, keycode 191 (keysym 0x1008ff81, XF86Tools), same_screen YES,
    XKeysymToKeycode returns keycode: 179
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False


This is a regression - it worked fine in Fedora 18 (gnome 3.6). I've tried disabling the shortcut and re-setting it just in case there was old config, but that didn't help.
Comment 1 Bastien Nocera 2014-11-09 23:55:51 UTC
Is this still a problem with newer versions of GNOME?
Comment 2 Tim Cuthbertson 2014-11-10 01:12:25 UTC
I just re-tested on GNOME Shell 3.10.4 (fedora 20), and yes, it's still a problem here. I will test again on fedora 21 when I upgrade.
Comment 3 Florian Müllner 2014-11-10 10:24:02 UTC
3.10.4 is about a year old by now and no longer maintained upstream, so it doesn't really qualify as "newer version of GNOME".
Comment 4 Tim Cuthbertson 2015-02-02 11:49:57 UTC
I have just upgraded, and can confirm that this is still an issue on fedora 21, with gnome-shell 3.14.3
Comment 5 Bastien Nocera 2017-05-31 13:32:45 UTC
And all those years later, and it's been root-caused and fixed in the development version for GNOME 3.26.

Please mention on the duplicate bug if you want this problem backported.

Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 781223 ***