asus multimedia hotkeys not handled

Bug #37225 reported by Nicolò Chieffo
20
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Fix Released
Medium
Unassigned
xkeyboard-config (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

ASUSTeK Computer Inc.
M6Ne
1.0

Play/next 0xa2 or XF86AudioPlay
stop 0xa4 or XF86AudioStop
previous 0x90 or XF86AudioPrev
next 0x99 or XF86AudioNext

I'm using latest upgrade packages and I've just created a new user. unfortunately these keys are not handled!

Tags: keyboard
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

It is simple to get this hotkeys working: go to system, preferences, keyboard shortcuts and set them! there's an audio section!
anyway this must be done by default, not requiring user interaction!

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I just created a new user to see how they are handled now, but again everything is set to disabled in keyboard shurtcuts!

Revision history for this message
Paul Sladen (sladen) wrote :

We need to map all the 'xf86*' keys to match the kernel 'input.h'...

Changed in hotkey-setup:
status: Unconfirmed → Confirmed
Revision history for this message
Paul Sladen (sladen) wrote :

...and to set 'gnome-keybinding-properties' to have these already setup.

Changed in control-center:
status: Unconfirmed → Confirmed
Revision history for this message
Nicolò Chieffo (yelo3) wrote : Re: [Bug 37225] Re: asus multimedia hotkeys not handled

ok! can I but I must add an information! the real keycodes are not
XF86*! these keycodes appears to be generated only if I first set the
?x?? in keyboard shortcuts! so we can base on these only if they are
set!

On 4/4/06, Paul Sladen <email address hidden> wrote:
> ...and to set 'gnome-keybinding-properties' to have these already setup.
>
> ** Changed in: control-center (Ubuntu)
> Status: Unconfirmed => Confirmed
> --
> asus multimedia hotkeys not handled
> https://launchpad.net/malone/bugs/37225
>

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

dapper final released! I hoped this could be fixed soon...

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

hello I'm testing hotkeys with edgy! everything is enabled except:

next track (0x99)
previous track (0x90)
stop (0xa4)

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Whith the latest edgy I've noticed that the keycode 0xa2 is associated wirh PAUSE but it's PLAY/PAUSE!!!

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

the same with feisty...
could we have it fixed? where are the default keys located? which package?

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

proposed patch that should fix it

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

the bug is in the gconf default settings

Changed in xkeyboard-config:
status: Confirmed → Rejected
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

this attachment is the patch to the source code. sorry for the previous ones

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you Nicolò. Matthew, do you know if those key codes are standard?

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

my hotkeys are mapped to acpi_fakekey which uses the consant in
/usr/include/linux/input.h

if they are not standard, also input.h is wrong

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the work, I've updated the previous patch to list extra actions:

 control-center (1:2.18.1-0ubuntu2) feisty; urgency=low
 .
   * debian/patches/07_default_keys.patch:
     - updated keycodes (play, pause, previous, next) (Ubuntu: #37225)

Changed in control-center:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.