This is very similar bug to two bugs already fixed (or hacked): Bug #347623: "Samsung q45 does not produce key-release events for Fn-Keys (patch included)" Bug #295251: "Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect "
It seems that for every new laptop, SAMSUNG produce malfunctioning keyboards, which for some of Fn + XX keys does not sent key-released events. Bugs mentioned above, and this one, introduce two patches, one patch for atkbd.c about adding artificial key-release events. And other patch for HAL to add these laptops models to definition of Samsung keyboard, so users have not to use setkeycodes for every Fn + XX combination. If I learn my laptop to recognize for eg. brightness keys with: setkeycodes e008 225 # brightness up setkeycodes e009 224 # brightness down placed in /etc/rc.local, or HAL patch, than xev shows key-pressed event but no key-release, it produce infinite sample of auto repeated key events - which locks computer. Would it be possible to introduce same patches as for "Samsung q45 and Samsung NC10 also for Samsung X360 ? I have found exactly same problem in lanchpad for Samsung R518, R60, NC20, Q35, Q210. Eg. Bug #360247, Bug #411031, Bug #253874, Bug #385683, etc. Maybe it will be good to introduce a patch for all Samsung laptops, as all seems to have malfunctioning keyboards? Or to prepare a common, unified bug, where people could place their laptop models to be added to a common patch, without need of filling separate bug reports? ** Attachment added: "lshal for Samsung X360" http://launchpadlibrarian.net/30647212/lshal.txt -- samsung x360 fn-keys work incorrectly https://bugs.launchpad.net/bugs/399911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
