[Possible Regression] Microsoft Keyboard favourite keys not producing scan code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Microsoft Wireless Keyboard 3000 favourite buttons (labelled "1", "2", "3", "4", "5") as well as the key with cascading windows on it (in a position of SUPER_R) do not produce any scancodes or acpi_events at all.
Some debugging information from hotkeys troubleshooting:
> ~$ sudo /lib/udev/
USB keyboard: input/event4
USB keyboard: input/event6
USB keyboard: input/js0
AT keyboard: input/event3
module: input/event8
The input/event4 is for regular keys, input/event6 is for special keys. input/js0 is (probably another) bug?
Probably irrelevant:
> ~$ cat /sys/class/
ASUSTeK Computer Inc.
> ~$ cat /sys/class/
M50Vn
This what happens when I click the buttons with keymap -i:
> ~$ sudo /lib/udev/keymap -i input/event6
Press ESC to finish
^C
(Nothing)
Acpi_listen:
> ~$ acpi_listen
^C
(Also Nothing)
This bug is related to this (and it was fixed in intrepid, I assume) but it is probably another regression on the issue.
https:/
All other buttons (except these 6 work fine) (except for the zoom in / zoom out due to scan codes > 256, witch is not the problem for the bug)
I am attaching various dumps from the howtos. Please tell me if I am missing something, as I do not have a clue how to diagnose this.
The dumps attached:
dmesg.log
lspci-vnvn.log
orig-map.txt
udev-db.txt
uname-a.log
version.log
tags: | added: kj-triage |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 663034
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.