Bug 11520 - Please support for Unitek KB-2125 keyboard's multimedia keys
Please support for Unitek KB-2125 keyboard's multimedia keys
Status: RESOLVED FIXED
Product: xkeyboard-config
Classification: Unclassified
Component: General
unspecified
Other All
: medium normal
Assigned To: xkb
http://bugs.debian.org/cgi-bin/bugrep...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-09 15:35 UTC by Mohammed Adnène Trojette
Modified: 2008-01-13 11:43 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mohammed Adnène Trojette 2007-07-09 15:35:36 UTC
Here is a Debian bug report (#259632).

From: Nicolas DEGAND <nicolas.degand@laposte.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: xkb: Unitek KB-2125 multimedia keys not supported
Date: Thu, 15 Jul 2004 21:32:33 +0200

Package: xlibs
Version: 4.3.0.dfsg.1-6
Severity: normal

The multimedia keys of the keyboard are not recognized. I have collected 
their names with xev, but do not know how to implement them :

brandname = "Unitek"
modelname = "Internet & Multimedia Keyboard KB-2125 (21 keys)"

 [KEYS]

Calculator =161
My Computer =235
Media =237
Back =234
Forward =233
Stop =232
Refresh =231
Mute =160
MMStop =164
Search =229
Favorites =230
Home =178
Email =236
Previous =144
Next =153
Play|Pause =162
VolumeUp =176
VolumeDown=174
Wake =227
Sleep =223
Power =222
Comment 1 Sergey V. Udaltsov 2007-07-10 06:30:03 UTC
Look at the file symbols/inet, you'll find a number of definitions similar to the one you need. They are using the keycodes defined in keycodes/xfree86.

So, looking forward to getting a patch for symbols/inet from you;)
Comment 2 Benjamin Close 2008-01-11 02:39:04 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 3 Mohammed Adnène Trojette 2008-01-13 11:43:49 UTC
The bug submitter does not own this keyboard anymore. I intended to close this bug, but I didn't know what resolution I should use. Feel free to do it.