FS#28049 - udev 178-1: Wrong keymap

Attached to Project: Arch Linux
Opened by TF (Johnny_Five) - Sunday, 22 January 2012, 14:12 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 24 January 2012, 23:33 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since the upgrade from 175 to 178 udev does not load the correct keymap file on my Samsung netbook.
Keys like BrightnessUp/Down and a bunch of others do not work.

The correct keymap is samsung-other and it should be loaded from 95-keymap.rules, line 141:
ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", RUN+="keymap $name samsung-other"

$ cat /sys/class/dmi/id/{sys_vendor,product_name}
SAMSUNG ELECTRONICS CO., LTD.
N145P/N250P/N260P

Manual loading of the keymap (# sudo /lib/udev/keymap -i input/event0 samsung-other) fixes the issue.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 24 January 2012, 23:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  udev-179 is in [testing]
Comment by George Brooke (GeorgeB) - Sunday, 22 January 2012, 14:44 GMT
Same on my Thinkpad T61,

95-keymap.rules line;
ENV{DMI_VENDOR}=="LENOVO*", KERNELS=="input*", ATTRS{name}=="ThinkPad Extra Buttons", RUN+="keymap $name module-lenovo"

$ cat /sys/class/dmi/id/sys_vendor
LENOVO

Manual loading, as in the original report, solves the problem until the next reboot.
Comment by Alec Bickerton (abickerton) - Sunday, 22 January 2012, 18:48 GMT
The same thing on a R60 thinkpad. Manual reloading module-lenovo does not resolve the issue.
Comment by Ionut Biru (wonder) - Sunday, 22 January 2012, 18:52 GMT
you guys should really report upstream about this issue.
Comment by TF (Johnny_Five) - Sunday, 22 January 2012, 19:15 GMT Comment by TF (Johnny_Five) - Sunday, 22 January 2012, 21:30 GMT
Upsteam says it is a bug with $name, which should be expanded to input/eventX instead of the current eventX. Should be fixed in the next udev-release.
Quick fix: change your RUN+="keymap $name keymap" to RUN+="keymap input/$name keymap"
Comment by Tom Gundersen (tomegun) - Sunday, 22 January 2012, 22:19 GMT
@Tobias: could you point me to the relevant email/patch? I was not able to find a solution on the ml/git. I'd be happy to backport a fix that is going in -179.
Comment by TF (Johnny_Five) - Sunday, 22 January 2012, 22:29 GMT
It kinda happened outside the ml, due to a mistake on my part. Kay Sievers concluded:

It's a bug in $name. It's a very old bug, but exposed only in the
recent udev versions. I'll fix it.

Thanks,
Kay
Comment by Tom Gundersen (tomegun) - Sunday, 22 January 2012, 22:49 GMT
@Tobias: thanks. I'll backport as soon as a fix appears in git (as I'm not 100% sure what the correct fix should be).
Comment by TF (Johnny_Five) - Monday, 23 January 2012, 07:48 GMT Comment by ajaxas (ajaxas) - Monday, 23 January 2012, 17:30 GMT
What if that fix doesn't help?
Sorry, but I put the description here: https://bbs.archlinux.org/viewtopic.php?pid=1046260 - seems similar, only in my case loading keymap manually or using udev-git doesn't solve the problem. :(
Comment by Tom Gundersen (tomegun) - Tuesday, 24 January 2012, 23:15 GMT
@Tobias: thanks. New release being built as we speak :)

@ajax: if the new release does fix it for you please open a new bug report as this sounds like a different bug. Before you do, please check that there are no stale (not owned by any package) files under /lib/udev/. Or maybe following up on the ml message you posted and let them know the status after the upgrade would be more efficient :)

Loading...