Bug 986653 - Dell brightness keys register multiple times
Summary: Dell brightness keys register multiple times
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-21 10:35 UTC by Bradley
Modified: 2014-06-18 14:02 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-18 14:02:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bradley 2013-07-21 10:35:51 UTC
Description of problem:

I've got a new Dell laptop that I've installed F19 on. When using the brightness down/up hotkeys (FN-F4/FN-F5), each key registers three times.

The three times happen from:

 - the dell-wmi module (if I rmmod that, I get only two key presses)
 - the systemd keymaps for dell laptops (if I use the keymap util to map those keys from brightness{up,down} to unknown, that removes another key press)
 - ACPI

Version-Release number of selected component (if applicable):

systemd-204-9.fc19.x86_64
kernel-3.9.9-302.fc19.x86_64

How reproducible:

Always

Steps to Reproduce:

1. Press fn-F[45] while in X.

Actual results:

XFCE brightness monitor goes in steps of 3

Expected results:

XFCE brightness adjusts in steps of 1

Additional info:

I can use the panel app (or echoing to the appropriate sysfs file) to set the brightness manually - this is solely a key-related issue (I have to boot with acpi_backlight=vendor for that, though)

The dell-laptop and i8k modules are loaded, but doesn't seem to make a difference either way

showkey -s output:

press any key (program terminates 10s after last keypress)...
0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 
0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 
0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4 
0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4 
0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 
0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 

/usr/lib/udev/keymap -i input/event3 :

Press ESC to finish, or Control-C if this device is not your primary keyboard
scan code: 0x85   key code: brightnessdown
got scan code event 0x85 without a key code event
scan code: 0x86   key code: brightnessup
got scan code event 0x86 without a key code event
scan code: 0x01   key code: esc

# acpi_listen 
 PNP0C14:00 000000d0 00000000
video/brightnessup BRTUP 00000086 00000000
video/brightnessdown BRTDN 00000087 00000000
 PNP0C14:00 000000d0 00000000

(first two lines are from me pushing the UP combination; last two are pressing the DOWN one once. This is in X)

Comment 1 Josh Boyer 2013-09-18 20:34:17 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Bradley 2013-09-22 10:11:31 UTC
Still an issue

Comment 3 Justin M. Forbes 2014-02-24 13:58:48 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Bradley 2014-03-01 12:24:03 UTC
Still an issue with 3.13.3-201.fc20.x86_64

Comment 5 poma 2014-04-30 19:09:56 UTC
Possible duplicates - Brightness related:

Brightness adjustment FN keys doesn't work
https://bugzilla.redhat.com/show_bug.cgi?id=702352

Brightness/backlight keys (fn+F8, fn+F9) does not work on lenovo T530 out of the box
https://bugzilla.redhat.com/show_bug.cgi?id=947976

Acer Aspire V5-171-9620 display brightness doesn't change using keyboard Fn keys (but onscreen slider moves)
https://bugzilla.redhat.com/show_bug.cgi?id=983342

unable to adjust monitor brightness with nouveua, Toshiba, and 3.11.0 kernel
https://bugzilla.redhat.com/show_bug.cgi?id=999684

Cannot adjust brightness anymore using Fn keys with F19 x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1012674

Brightness does not change on Intel graphics (using keys or slider) since about 3.9 kernels
https://bugzilla.redhat.com/show_bug.cgi?id=1025690

Brightness keys stopped working between kernel 3.12.10-300 and 3.13.3-201 on Asus EEE PC
https://bugzilla.redhat.com/show_bug.cgi?id=1067181

T530: Unsupported brightness interface
https://bugzilla.redhat.com/show_bug.cgi?id=1089545

Can't change display brightness on HP EliteBook 8470p
https://bugzilla.redhat.com/show_bug.cgi?id=1093120

Comment 6 Justin M. Forbes 2014-05-21 19:39:33 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 7 Josh Boyer 2014-06-18 14:02:40 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.