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 351305 - Keybindings in group "Sound" blocking normal keys
Keybindings in group "Sound" blocking normal keys
Status: RESOLVED DUPLICATE of bug 133815
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-14 15:08 UTC by Martin Ammermüller
Modified: 2006-09-22 13:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Martin Ammermüller 2006-08-14 15:08:04 UTC 
Please describe the problem:
When binding any of "play (or play/pause)", "pause", "stop playback key" or "skip to previous track" in group "Sound" to <keychain><anykey>, where <keychain> is any supported combination of <Alt>, <Ctrl>, <Shift> and <AltGr>, <anykey> stops working in all other application in the running X-Session.

Steps to reproduce:
1. Start gnome-keybindings-properties
2. Assign <keychain><anykey> to any of the mentioned bindings above
3. Try to type <anykey> in a application running in the current X-Session


Actual results:
<anykey> stops working in X-Session

Expected results:
<anykey> still works in X-Session

Does this happen every time?
Yes.

Other information:
This issue is ages old. I know it since Ubuntu Hoary, which should translate to Gnome Version 2.10.x, AFAIK. I think a similar bug was filed already, but couldn't find it anymore.
Comment 1 Daniel Holbach 2006-09-12 17:39:02 UTC 
Mentioned in https://launchpad.net/distros/ubuntu/+source/control-center/+bug/40747 as well.
Comment 2 Bastien Nocera 2006-09-22 13:59:26 UTC 
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 ***