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 154944 - [PATCH]Invalid key assignment on the second keybinding setup for multimedia events
[PATCH]Invalid key assignment on the second keybinding setup for multimedia e...
Status: RESOLVED DUPLICATE of bug 133815
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
git master
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 315279 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-10-08 22:58 UTC by Michal Bukovjan
Modified: 2006-09-22 14:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A possible way to fix the problem. (1023 bytes, patch)
2004-10-08 23:00 UTC, Michal Bukovjan 		none Details | Review

Description Michal Bukovjan 2004-10-08 22:58:36 UTC 
When I try to set up an event that works via a remapped key (for example, Next
track, unassigned/disabled yet):

1. When pressing a next track key on my multimedia keyboard, a 0x99 symbols
appears. This is correct and the key works.
2. When I try to assign the same key to the same event for a second time,
XF86AudioNext is displayed and the key does not work.
3. When I repeat the assignment again, 0x99 is assigned and it works again.

I expect the key to work any time I assign it.

I have a (not very elegant) patch to fix this problem.
Comment 1 Michal Bukovjan 2004-10-08 23:00:29 UTC 
Created attachment 32414 [details] [review]
A possible way to fix the problem.

Unfortunately, the XF86 keysym range does not seem to be defined anywhere via
defines, therefore this constants :-\
Comment 2 Sebastien Bacher 2005-10-23 12:05:17 UTC 
*** Bug 315279 has been marked as a duplicate of this bug. ***
Comment 3 Vidar Braut Haarr 2005-11-11 21:37:36 UTC 
I just found that this bug also occurs on my laptop, which has a clean Ubuntu
Breezy install which is now tracking Ubuntu Dapper and, of course, a completely
different hardware configuration than my desktop computer.

Is there anything I can do to help out? What is wrong with bukovjan's patch?

I guess I could try attachment 32424 [details] -- I'll probably have time for that tomorrow.
Comment 4 Vidar Braut Haarr 2005-11-19 22:53:44 UTC 
I just witnessed this bug on a fresh install of Ubuntu Breezy with en-US locale,
if it should matter in any way ...
Comment 5 Bastien Nocera 2006-09-22 14:13:05 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 ***