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 139190 - Keyboard Shortcuts doesn't work with Logitech keyboard's extra keys
Keyboard Shortcuts doesn't work with Logitech keyboard's extra keys
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.6.x
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 139061 139219 139305 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-05 21:07 UTC by bugs-gnome
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description bugs-gnome 2004-04-05 21:07:19 UTC
Distribution: Gentoo Base System version 1.4.3.13p1
Package: control-center
Severity: normal
Version: GNOME2.6. 2.6.x
Gnome-Distributor: Gentoo Linux
Synopsis: Keyboard Shortcuts doesn't work with Logitech keyboard's extra keys
Bugzilla-Product: control-center
Bugzilla-Component: Keybinding
Bugzilla-Version: 2.6.x
Description:
Description of Problem:
In 2.6's Keyboard Shortcuts control center dialog, trying to set a
shortcut to an extra button on my Logitech Elite keyboard is rather
broken.

Steps to reproduce the problem:
1. Open Keyboard shortcuts
2. Left click any shortcut (to set)
3. Press any extended key (email, next song, volume up, whatever)

Actual Results:
Warning dialog:  'The shortcut "0xa0" is already used for: "Launch Help
Browser"'

Expected Results:
Action binded to key

How often does this happen?
Every time

Additional Information:

"Launch Help Browser" at the moment is actually the first item marked as
disabled. Enabling it to some dummy value results in the error message
claiming that the keycode is used for the next Disabled item. Setting
the first Disabled item to an extra key results in the one after it
being in the error message.

This worked flawlessly with ACME, so the likelyhood of it being a
software bug is great.

The xev output for the keypress of the button used in the example (the
mute button) follows:

KeyRelease event, serial 26, synthetic NO, window 0x2a00001,
    root 0x46, subw 0x0, time 45015859, (-392,82), root:(690,396),
    state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:  ""




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-05 17:07 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "control-center".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was bugs-gnome@pocketninja.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Jody Goldberg 2004-04-06 16:56:05 UTC
*** Bug 139219 has been marked as a duplicate of this bug. ***
Comment 2 Jody Goldberg 2004-04-06 17:06:41 UTC
Fixed in cvs.
Patch will be in 2.6.1
Comment 3 Jody Goldberg 2004-04-06 17:07:18 UTC
*** Bug 139061 has been marked as a duplicate of this bug. ***
Comment 4 Jody Goldberg 2004-04-06 17:11:45 UTC
Fixed in cvs.
Patch will be in 2.6.1
Comment 5 Jody Goldberg 2004-04-06 17:55:23 UTC
doh!
It would help to actually close the damn thing
Comment 6 Jody Goldberg 2004-04-14 17:45:27 UTC
*** Bug 139305 has been marked as a duplicate of this bug. ***