Multimedia keys on ASUS got assigned same scan code

[Saulius Lukauskas]

Binary package hint: udev

Hotkeys of multimedia buttons get assigned same scan code 0x00 in sudo /lib/udev/keymap -i input/event8
Like this:
> ~$ sudo /lib/udev/keymap -i input/event8
Press ESC to finish
scan code: 0x00 key code: screenlock
scan code: 0x00 key code: 14A
scan code: 0x00 key code: prog1
scan code: 0x00 key code: email
scan code: 0x00 key code: www
scan code: 0x00 key code: nextsong
scan code: 0x00 key code: previoussong
scan code: 0x00 key code: playpause
scan code: 0x00 key code: stopcd

Though the key codes differ are mostly correct (except for screenlock, which is run key (fn+space) and 14A which is for touchpad turn on/off) and I am not sure about prog1)

the keydump consists of single line:
> ~$ sudo /lib/udev/keymap input/event8
### evdev 1.0.0., driver 'Asus Laptop extra buttons'

acpi_listen detects the keys as:

> ~$ acpi_listen
hotkey ATKD 0000005c 00000046
hotkey ATKD 0000006b 00000021
hotkey ATKD 0000008a 0000000d
hotkey ATKD 00000050 00000004
hotkey ATKD 00000051 00000004
hotkey ATKD 00000041 0000001c
hotkey ATKD 00000040 00000008
hotkey ATKD 00000045 00000006
hotkey ATKD 00000043 00000004

xev detects keys as:

FocusOut event, serial 38, synthetic NO, window 0x4c00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 38, synthetic NO, window 0x4c00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 38, synthetic NO, window 0x0,
    keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

lshal -m detects some of the keys:
> ~$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
15:53:10.980: computer_logicaldev_input_3 condition ButtonPressed = coffee
15:53:15.549: computer_logicaldev_input_3 condition ButtonPressed = email
15:53:15.937: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = mail
15:53:19.159: computer_logicaldev_input_3 condition ButtonPressed = www
15:53:25.737: computer_logicaldev_input_3 condition ButtonPressed = next-song
15:53:26.477: computer_logicaldev_input_3 condition ButtonPressed = previous-song
15:53:28.199: computer_logicaldev_input_3 condition ButtonPressed = play-pause
15:53:28.741: computer_logicaldev_input_3 condition ButtonPressed = stop-cd

Release of ubuntu:
> ~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

> ~$ apt-cache policy udev
udev:
  Installed: 147~-6
  Candidate: 147~-6
  Version table:
 *** 147~-6 0
        500 http://lt.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Product:
> ~$ cat /sys/class/dmi/id/sys_vendor
ASUSTeK Computer Inc.
> ~$ cat /sys/class/dmi/id/product_name
M50Vn
This does not allow to change the key bindings as all scan codes are the same.
Expected behaviour: different scan codes

[Jeremy Foshee (jeremyfoshee)]

Hi Saulius,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 466907

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]