[Hotkey] EeePC 901 wrong keycode on Changescreen Key

Bug #350590 reported by David Iwanowitsch on 2009-03-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: xkeyboard-config

I am using Jaunty Beta with all updates

My EeePc has a key (FN+F5) for detecting external Displays. When pressing the key
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
reports:
keycode 235 = (keysym 0x1008ff59, XF86Display), state = 0x0
keycode 235 = (keysym 0x1008ff59, XF86Display), state = 0x0
keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x0
keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x0

the first 2 lines come from "Asus EeePC extra buttons"
david@eeeTesting:~$ sudo input-events 9
/dev/input/event9
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x0
   version : 0
   name : "Asus EeePC extra buttons"
   phys : "eeepc/input0"
   bits ev : EV_SYN EV_KEY

waiting for events
22:28:19.516836: EV_KEY KEY_SWITCHVIDEOMODE (0xe3) pressed
22:28:19.516880: EV_SYN code=0 value=0
22:28:19.516928: EV_KEY KEY_SWITCHVIDEOMODE (0xe3) released
22:28:19.516939: EV_SYN code=0 value=0

The last two lines from "AT Translated Set 2 keyboard"
david@eeeTesting:~$ sudo input-events 5
/dev/input/event5
   bustype : BUS_I8042
   vendor : 0x1
   product : 0x1
   version : 43841
   name : "AT Translated Set 2 keyboard"
   phys : "isa0060/serio0/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
22:30:13.119061: EV_KEY KEY_VOLUMEUP (0x73) pressed
22:30:13.122658: EV_KEY KEY_VOLUMEUP (0x73) released

David Iwanowitsch (dav.id) wrote :

I was not sure where to report this Bug.
https://wiki.ubuntu.com/Hotkeys/Troubleshooting says:
3 c) if the keycode itself is wrong, this is a bug in xkeyboard-config.
10) If the events are reported by more than one input device then report a kernel bug (Ubuntu linux package) because it should only send the event on one device.

I have choosen the first, sorry if this is wrong.

Changed in xkeyboard-config:
status: New → Confirmed
Bryce Harrington (bryce) on 2009-09-02
tags: added: jaunty
Bryce Harrington (bryce) wrote :

Given that you're getting it reported by two devices I think this needs to be analyzed as a kernel bug first.

affects: xkeyboard-config (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → New
Jeremy Foshee (jeremyfoshee) wrote :

Hi David,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please 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 350590

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.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers