Many Laptops (e.g. Fn keys on many samsung models) do not send key-release events

Bug #478441 reported by Zem on 2009-11-08
This bug report is a duplicate of:  Bug #554066: Samsung N220 hotkeys don't work. Edit Remove
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
udev (Ubuntu)

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: (Samsung R60) (Samsung nc20) (Samsung q45) (Samsung P560) (Samsung Q210) (samsung x360)

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.

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.

Zem (internetschmuddel) on 2009-11-11
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
Jeremy Foshee (jeremyfoshee) wrote :

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 .

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 . 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.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
ldm (lucky-dm-77) wrote :


I have a Samsung Q45 and I'm an Ubuntu user since Feisty Fawn.
I have read a lot about 'Fn keys' on Samsung laptops in bugzilla and also in
This bug has been marked as fixed, but it is still present! (also in Lucid Lynx
with kernel 2.6.32-22)

Anyway yesterday I have tried this solution and it works fine:
package 'samsung-backlight' enables brightness up/down
package 'samsung-tools' enables wireless on/off

It seems to use DKMS (Dynamic Kernel Module Support),
it is possible to include this code directly in linux kernel source tree?

ldm (lucky-dm-77) wrote :


the answer of the developer for this bug:

'You need to talk to your distribution to make sure that they apply
force_release workaround upon booting the box.'

so can you please include this patch in ubuntu kernel?

Keng-Yu Lin (lexical) wrote :

In lucid udev is responsible for this. You can add quirking in "/lib/udev/rules.d/95-keyboard-force-release.rules" and check "/lib/udev/keymaps/force-release/samsung-other" for keys to be force_released.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
ldm (lucky-dm-77) wrote :

Ubuntu 10.10 and bug still present on Samsung Q45

ldm@Q45:~$ cat /sys/class/dmi/id/sys_vendor
ldm@Q45:~$ cat /sys/class/dmi/id/product_name


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.