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 311741 - Next / previous track keyboard shortcuts don't work correctly
Next / previous track keyboard shortcuts don't work correctly
Status: RESOLVED DUPLICATE of bug 133815
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-27 15:37 UTC by Radu
Modified: 2006-09-22 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Radu 2005-07-27 15:37:41 UTC
Version details: gnome-base/gnome-2.10-r1
Distribution/Version: gentoo

1. Go to Keyboard Shortcuts
2. Under Sound, select the "Skip to next track" action
3. Hit <Shift><Control>F7

You will see that <Shift><Control>F7 is bound to "Skip to next track". Now the
problem is that only F7 will be bound to that action, not <Shift><Control>F7...
That is, everytime you press F7, the action will be triggered. That also happens
if you press <Alt>F7 (so you can't move the windows anymore with <Alt>F7). This
also happens if you assign, for example, <Shift><Alt>k - it won't trigger when
you press <Shift><Alt>k, but rather when you simply press k.

The same thing happens if you assign a shortcut to "Skip to previous track" or
"Play (or play/pause)", but if you do the exact same thing for "Volume up" or
"Volume down", it works - it only turns the volume up if you press
<Shift><Control>F7 and it doesn't mess up the <Alt>F7 shortcut.
Comment 1 Sergej Kotliar 2005-07-28 01:52:15 UTC
I can confirm this with control-center 2.11.6 (development version).

Very weird in deed. Seems to be previously unreported though...
Comment 2 Nigel Tao 2005-08-18 17:32:28 UTC
Possibly related to bug 133815?
Comment 3 Bastien Nocera 2006-09-22 13:49:43 UTC
Exact same one actually.

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.


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