Bugzilla – Bug 1082104
Display brightness won't change using Fn keys
Last modified: 2018-02-21 19:47:28 UTC
Created attachment 761113 [details] Hardware Information After updating Tumbleweed 01/02/2018 to 20/02/2018, just the Fn keys in my laptop's keyboard that controls display brightness stopped working. I still can change display brightness through "Battery and Brightness" tray icon in my panel (although there are some minor graphical glitches as I move the ball on the bar). The same thing happened when I upgraded to latest KDE/Qt on my OpenSUSE Leap 42.3. Under these conditions, the bug is always reproducible. Since this tumbleweed update upgraded plasma 5.11 to plasma 5.12, could it be related to KDE/Qt?
Possible related problem, although not tested: https://bbs.archlinux.org/viewtopic.php?id=178014
(In reply to Felipe Abrahao from comment #1) > Possible related problem, although not tested: > https://bbs.archlinux.org/viewtopic.php?id=178014 Then it would not be related to KDE/Qt though... ;-) I assume this is https://bugs.kde.org/389991 though, a problem with migrating the powermanagement keyboard shortcuts. It should be fixed in Plasma 5.12.2, that has been released yesterday (not in the repos yet though).
PS: https://bugs.kde.org/show_bug.cgi?id=389991#c22 explains how to fix it yourself. You could try that and see if the keys work again afterwards.
(In reply to Wolfgang Bauer from comment #2) > (In reply to Felipe Abrahao from comment #1) > > Possible related problem, although not tested: > > https://bbs.archlinux.org/viewtopic.php?id=178014 > > Then it would not be related to KDE/Qt though... ;-) > > I assume this is https://bugs.kde.org/389991 though, a problem with > migrating the powermanagement keyboard shortcuts. > > It should be fixed in Plasma 5.12.2, that has been released yesterday (not > in the repos yet though). Thanks!
Actually there already is a bug report about this problem, so I'll mark this as duplicate. Feel free to reopen if your problem is not fixed with Plasma 5.12.2 (as it likely is a different problem then). *** This bug has been marked as a duplicate of bug 1078487 ***