Bug 436530 - Fn+F7 stopped working on Slimbook under Neon
Summary: Fn+F7 stopped working on Slimbook under Neon
Status: RESOLVED UPSTREAM
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-03 11:59 UTC by Daniel Duris
Modified: 2021-05-03 21:22 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Duris 2021-05-03 11:59:14 UTC
SUMMARY
Fn+F7 does not work anymore (keyboard backlight function). F7 alone works OK, I can assign actions to it in Shortcuts. Fn+F7 does not work. Fn+F8 works (Mute) etc. I am also unable to assign action to Fn+F7 in Shortcuts (key does not register).

I get this log in dmesg:
[92247.850913] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[92247.850921] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[92249.590612] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
[92249.590618] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.

STEPS TO REPRODUCE
1. Press Fn+F7
2. 
3. 

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Backlight changes (or any other assigned function triggers).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Neon 5.21
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel 5.10.4

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-05-03 19:06:16 UTC
What specific model do you have?
Comment 2 Daniel Duris 2021-05-03 19:33:49 UTC
(In reply to Nate Graham from comment #1)
> What specific model do you have?

PRO X14
Comment 3 Nate Graham 2021-05-03 21:22:04 UTC
Seems like a kernel bug. Looks like it lost the mapping for this key, for some reason. I would recommend reporting the bug to https://bugzilla.kernel.org/

Thanks!