[Bug 1105997] New: Keyboard Brightness keys do not change keyboard brightness
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997 Bug ID: 1105997 Summary: Keyboard Brightness keys do not change keyboard brightness Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: noahadvs@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Build Identifier: fn+F3 and fn+F4 are detected by KDE Plasma (5.13.4) as "Keyboard Brightness Down" and "Keyboard Brightness Up" as they should be, but they do not actually change the brightness as of kernel 4.17.14 and 4.18.0 and . I suspect this is a kernel bug because fn+F3/fn+F4 work as they should in the Leap 15 KDE live image (kernel 4.12.14-lp150.12.4-default, Plasma 5.12) and KDE Neon User Edition 20180823 live image (kernel 4.15, Plasma 5.13). Reproducible: Always Steps to Reproduce: 1. Use kernel 4.17.14 or 4.18.0 2. Press fn+F3 or fn+F4 Actual Results: Keyboard brightness does not change and I don't get an on-screen display from Plasma showing the keyboard brightness level. Expected Results: Keyboard brightness should go through 4 levels (off, 33%, 67%, 100%) when using the keyboard brightness keys and Plasma should show an on-screen display with the current keyboard brightness level. I have an ASUS K501UW laptop with an LED backlit keyboard. When 4.17 was first released for Tumbleweed, the keyboard didn't work at all until a fix was backported from kernel 4.18.0rc1. It's possible that this bug has been around since 4.17 and I just hadn't bothered to change keyboard brightness until recently. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c1
--- Comment #1 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c2
--- Comment #2 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c3
--- Comment #3 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c4
--- Comment #4 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c5
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c6
--- Comment #6 from Noah Davis
Did you install the Leap 15.0 kernel on top of the rest TW user-space and test it? That's how to check whether it's a kernel regression.
Is it safe to do that? Should I use this https://build.opensuse.org/package/show/Kernel%3AopenSUSE-15.0%3ASubmit/kern... or the official Leap 15 kernel packages? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c7
--- Comment #7 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c8
--- Comment #8 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c9
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997 http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c10 Yums Yumschanged: What |Removed |Added ---------------------------------------------------------------------------- CC| |yuh555@gmail.com --- Comment #10 from Yums Yums --- Hi. Opensuse tumbleweed. Kernel 4.18.5-1-default KDE 5.13.4 module asus-nb-wmi - load ASUS ux430ua Fn+F3 & Fn+F4 - don't work backlighte keyboard. Fn+10/11/12 - volume control - don't work. Monitor backlight working fine by using menu slider. if i used >echo 0(1,2,3) >> /sys/devices/platform/asus-nb-wmi/leds/asus\:\:kbd_backlight/brightness - can control backlight is start notebook with KDE Neon User Edition 20180823 live image (kernel 4.15, Plasma 5.13) - all work -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c11
--- Comment #11 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c12
Rainer Klier
This problem still exists in Plasma 5.14.
I can confirm that -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c13
--- Comment #13 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c15
--- Comment #15 from Rainer Klier
All people who suffer from the problem: check whether the kernel emits any key events via the input device at the key combo. Go to VT1 (ctrl-alt-F1), login as root, install evtest package if not exists, then run evtest. Choose the appropriate device and try to push/release the key combo. If it doesn't show up on any input devices, it must be a kernel issue.
my results with the asus G750J notebook are the following: when running evtest (while in X session, not in console), it shows the following selection: No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: ETPS/2 Elantech Touchpad /dev/input/event2: Lid Switch /dev/input/event3: Sleep Button /dev/input/event4: Power Button /dev/input/event5: Video Bus /dev/input/event6: Asus Wireless Radio Control /dev/input/event7: PC Speaker /dev/input/event8: Asus WMI hotkeys /dev/input/event9: HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA NVidia HDMI/DP,pcm=3 /dev/input/event12: HDA NVidia HDMI/DP,pcm=7 /dev/input/event13: USB2.0 UVC HD Webcam: USB2.0 UV /dev/input/event14: Logitech Gaming Mouse G402 /dev/input/event15: Logitech Gaming Mouse G402 Keyboard /dev/input/event16: Logitech Gaming Mouse G402 Consumer Control /dev/input/event17: Logitech Gaming Mouse G402 System Control /dev/input/event18: Dell Dell USB Keyboard /dev/input/event19: Dell Dell USB Keyboard Consumer Control /dev/input/event20: Dell Dell USB Keyboard System Control Select the device event number [0-20]: if i select 0 (AT Translated Set 2 keyboard), the hotkey buttons for keyboard brightness do not create output. but, for example, the hotkeys for speaker volume create output. also hotkeys for screen brightness don't create output. if i select 8 (Asus WMI hotkeys) then the hotkeys for keyboard brightness create output. the hotkeys for screen brightness still don't create output. (but screen brightness might be controlled by nvidia closed source driver which i have installed.) the hotkeys for speaker volume don't create output. and i have the folder structure /sys/devices/platform/asus-nb-wmi/leds/asus\:\:kbd_backlight/ with the following contents: total 0 -rw-r--r-- 1 root root 4096 Oct 23 10:48 brightness lrwxrwxrwx 1 root root 0 Oct 23 10:48 device -> ../../../asus-nb-wmi -r--r--r-- 1 root root 4096 Oct 23 10:48 max_brightness drwxr-xr-x 2 root root 0 Oct 23 10:48 power lrwxrwxrwx 1 root root 0 Oct 23 10:48 subsystem -> ../../../../../class/leds -rw-r--r-- 1 root root 4096 Oct 23 10:48 trigger -rw-r--r-- 1 root root 4096 Oct 23 10:48 uevent and i can control brightness with echo 0(1,2,3) > /sys/devices/platform/asus-nb-wmi/leds/asus\:\:kbd_backlight/brightness so, it seems, that it is not a kernel issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c16
--- Comment #16 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c17
--- Comment #17 from Rainer Klier
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c18
--- Comment #18 from Rainer Klier
NEWS: today i updated to kernel 4.19.0 and suddenly the hotkey buttons for keyboard brightness work again! :-D
more news: a few days ago i updated my tumbleweed to: kernel 4.19.2 systemd 239 kde-plasma 5.14.3 kde-frameworks 5.52.0 Qt 5.11.2
but the GUI to control the brightness in KDE's energy settings are still missing. even when in the past they showed up.
and today i noticed: they are BACK!!! in the energy tray icon as well as in the energy settings. :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c19
--- Comment #19 from Noah Davis
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997
http://bugzilla.opensuse.org/show_bug.cgi?id=1105997#c20
--- Comment #20 from Rainer Klier
participants (1)
-
bugzilla_noreply@novell.com