Bug 62953 - udev has wrong keymap for keyboard, and sends wrong X event on key press
Summary: udev has wrong keymap for keyboard, and sends wrong X event on key press
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-30 23:16 UTC by bugspam
Modified: 2013-09-20 13:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
My current keymap (reported by xmodmap -pke) (9.66 KB, text/plain)
2013-03-30 23:16 UTC, bugspam
Details
xev log (157.66 KB, text/plain)
2013-03-30 23:17 UTC, bugspam
Details
Output from evtest (4.00 KB, text/plain)
2013-09-19 20:18 UTC, bugspam
Details
Grep output (1.14 KB, text/plain)
2013-09-19 20:18 UTC, bugspam
Details
Complete evtest output (5.74 KB, text/plain)
2013-09-19 20:27 UTC, bugspam
Details

Description bugspam 2013-03-30 23:16:03 UTC
Created attachment 77237 [details]
My current keymap (reported by xmodmap -pke)

udev has the wrong keymap for the keyboard of the Dell Studio XPS 1340 (2009 model). The key combination Fn + Right arrow is hard-wired by the system to switch the brightness of the keyboard backlight, however udev thinks it's "Touchpad Off" and sends the "XF86TouchpadOff" event. This makes it impossible to change the keyboard backlight brightness without stopping the KDE Touchpad Enabler service. 

FWIW, I was referred here from Kernel Bug 55521 (I originally thought this was a kernel issue). 

I'm using OpenSUSE 12.3 x64 with KDE 4.10.1, if that matters. 

I've attached my system keymap and a xev log that has the offending key combination.
Comment 1 bugspam 2013-03-30 23:17:53 UTC
Created attachment 77238 [details]
xev log
Comment 2 Lennart Poettering 2013-09-12 18:22:08 UTC
There's probably a key map that is wrongly applied for you laptop.

Martin might be able to help you, Martin?
Comment 3 Martin Pitt 2013-09-12 18:37:59 UTC
Can you please install the "evtest" tool, run it as root, select your keyboard, and press the broken keys? Use Control-C to abort, then copy&paste the output here together with some documentation which keys you pressed for which part of the output.

Please also give the output of

  grep . /sys/class/dmi/id/*

Thanks!
Comment 4 bugspam 2013-09-19 20:18:06 UTC
Created attachment 86163 [details]
Output from evtest

Output from evtest, during which I only pressed Fn+right arrow twice. No other keys were pressed, other than Ctrl+C to quit.
Comment 5 bugspam 2013-09-19 20:18:57 UTC
Created attachment 86164 [details]
Grep output

Output from the requested grep command
Comment 6 bugspam 2013-09-19 20:22:59 UTC
I apologize for my late reply. My android device wasn't properly syncing this email address and I didn't realize until now. 

I have attached everything that was requested. 

If this matters, in the intervening time (since 03/30) I've updated to KDE 4.11.1. And my kernel version is 3.7.10-1.16.
Comment 7 bugspam 2013-09-19 20:27:03 UTC
Created attachment 86165 [details]
Complete evtest output

The original got cut off somehow. This is complete and has the important parts.
Comment 8 Martin Pitt 2013-09-19 21:44:26 UTC
Thanks for the data. Indeed in the current keymaps we have some historical confusion about interpreting "F23", and our old keymaps imported from hal still sometimes used that for "Auto brightness". I cleaned up all of those (including your Dell) in  http://cgit.freedesktop.org/systemd/systemd/commit/?id=42a9de1c251
Comment 9 bugspam 2013-09-20 13:31:39 UTC
Thank you for fixing this issue. I hope the update to Systemd that contains this fix doesn't take too long to filter its way down to the distros (e.g. OpenSUSE).


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.