Many Laptops (e.g. Fn keys on many samsung models) do not send key-release events
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
udev (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
A lot of people are reporting missing keyboard key-release events, especially when using Laptop special Keys (e.g. Fn keys).
Small list of reports:
https:/
https:/
https:/
https:/
https:/
https:/
...
Each bug could get/was fixed by adding a model-specific quirk in atkbd.c.
linux 2.6.32 introduced a new generic mechanism using sysfs to add force-key-release quirks.
http://
I've a Samsung P55-Pro which also do not generate key-release events for the brightness up/down keys.
My suggestion is to backport the generic atkbd patch to the karmic kernel (2.6.31) so one can easily add key-release quirks (without patching and recompiling the kernel) using udev or similar mechanisms.
This way we don't need extra patches for each specific laptop model and we don't have to wait for lucid to be able to fix keys easily.
as a sidenote:
I wonder why my Fn keys do work on Hardy (didn't test Intrepid/Jaunty).
At least I'm not aware of any quirks which fix missing key-release events on Hardy for my Laptop.
summary: |
- Many Laptops (e.g. many samsung models) do not send key-release events + Many Laptops (e.g. Fn keys on many samsung models) do not send key- + release events |
description: | updated |
Hi Zem,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you 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 478441
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/KernelMainl ineBuilds . 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.]