| Summary: | Scancode of translated keys by hid-apple not displayed | ||
|---|---|---|---|
| Product: | evtest | Reporter: | Brice Waegeneire <brice.wge> |
| Component: | general | Assignee: | Peter Hutterer <peter.hutterer> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | brice.wge, peter.hutterer |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | attachment-455-0.html | ||
|
Description
Brice Waegeneire
2015-09-02 15:04:04 UTC
I doubt this is an evtest bug. evtest is simple enough that it'll just print whatever it gets. Especially the numeric value, and where it can't look up the name it'll display "?" instead. So if evtest isn't displaying the scancodes, they're not coming out of the kernel. > So if evtest isn't displaying the scancodes, they're not
> coming out of the kernel.
If they are not coming out of the kernel how can they be working in the tty and Xorg? By the way when they are remapped manually with udev they show up in evtest.
If this issue doesn't come from evtest where should I post it?
are they coming out of a different device node? No all the tests I did come from the same device `/dev/input/by-id/usb-Apple_Inc._Apple_Internal_Keyboard___Trackpad-event-kbd', a builtin keyboard of Macbook Air(mba4.2). run evtest without any arguments and it'll list all devices, see if there's one that looks promising and then check whether the keys are coming of of that. for some devices the kernel creates two device nodes and some keys, especially special keys, are then routed through the other device. Don't know if that's the case for this device, but let's verify it anyway. After testing the 13th devices only the 9th, the keyboard, display input when the problematic keys are pressed. # evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: Video Bus /dev/input/event5: PC Speaker /dev/input/event6: bcm5974 /dev/input/event7: FaceTime Camera (Built-in) /dev/input/event8: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event9: Apple Inc. Apple Internal Keyboard / Trackpad /dev/input/event11: HDA Intel PCH Headphone /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 Select the device event number [0-13]: sorry, this one dropped under the table. Closing it now, please re-open if this is still an issue The issue is still there and I still care about it since apple keyboards have a special layouts which is prone to users wanting to remap some of the keys. And the current workaround of going through wireshark to get them isn't straight forward at all. The keys that doesn't have scan codes are only the media/function keys and the "KEY_GRAVE". If you think the issue doesn't come from evtest, to whom I should address this? wait, when you mention scancodes are you talking about MSC_SCAN? or that nothing comes out of the keyboard at all? Created attachment 134635 [details] attachment-455-0.html Yes the value field of the line with MSC_SCAN. On other keyboards evtest return it for each keys. Here is an example from my first post where first the neter key is pressed and I get the value 70028 however when the media key previous is pressed it is missing the line MSC_SCAN and the value that I'm looking for. │ Event: time 1441205233.613742, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028 │ Event: time 1441205233.613742, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0 │ Event: time 1441205233.613742, -------------- SYN_REPORT ------------ │ Event: time 1441205235.605718, type 1 (EV_KEY), code 165 (KEY_PREVIOUSSONG), value 1 │ Event: time 1441205235.605718, -------------- SYN_REPORT ------------ 2017-10-03 10:04 GMT+02:00 <bugzilla-daemon@freedesktop.org>: > Peter Hutterer <peter.hutterer@who-t.net> changed bug 91853 > <https://bugs.freedesktop.org/show_bug.cgi?id=91853> > What Removed Added > Status REOPENED NEEDINFO > > *Comment # 9 <https://bugs.freedesktop.org/show_bug.cgi?id=91853#c9> on > bug 91853 <https://bugs.freedesktop.org/show_bug.cgi?id=91853> from Peter > Hutterer <peter.hutterer@who-t.net> * > > wait, when you mention scancodes are you talking about MSC_SCAN? or that > nothing comes out of the keyboard at all? > > ------------------------------ > You are receiving this mail because: > > - You are on the CC list for the bug. > - You reported the bug. > > oh, right. In that case you'll have to bring this up with the kernel. evtest doesn't filter on events and if we don't get a MSC_SCAN it's because the kernel didn't give us one. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.