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 332695 - Assigning Rhythmbox shortcut keys remaps key permanently
Assigning Rhythmbox shortcut keys remaps key permanently
Status: RESOLVED DUPLICATE of bug 133815
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.12.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-27 01:19 UTC by Joseph Hill
Modified: 2006-08-08 08:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Joseph Hill 2006-02-27 01:19:40 UTC
Please describe the problem:
After attempting to assign a shortcut to the sound player - skip to next track
function using <Ctrl><Shift>s, the "s" key became unusable, and "s" was
recognized as some hexidecimal value (0xf4 or something like that).  Resetting
the shortcut using the keybindings dialogue did not restore the key's function.
 I reset my keyboard settings using the Keyboard -> Layouts dialogue, which
appeared to work correctly, but on restarting X the problem recurs, and each
time I have to reset the defaults to get my "s" key to work.

Steps to reproduce:
1. Change the keyboard shortcut for Rhythmbox stop/play/pause/skip functions
2. 
3. 

Actual results:
The key I attempt to assign the shortcut gets remapped to a different value and
no longer works

Expected results:
The key combination would trigger the designated function in Rhythmbox and the
letter alone would continue to work

Does this happen every time?
Yes, I've reproduced it several times, meaning that several of my keys
consistently do not work when I restart X.

Other information:
Comment 1 Bastien Nocera 2006-08-08 08:23:38 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 ***