Bug 508457

Summary:	It should not be possible to assign Fn key (registerd as "Wake Up") as a single key shortcut as it then gets triggered all the time when using it in combinations
Product:	[Applications] systemsettings	Reporter:	tomashnyk
Component:	kcm_keys	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	CONFIRMED ---
Severity:	minor	CC:	duha.bugs, fanzhuyifan, kde, nate
Priority:	NOR	Keywords:	usability
Version First Reported In:	6.4.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description tomashnyk 2025-08-19 10:45:19 UTC

SUMMARY
Thinkpads (some? all? Mine is X1 Extreme Gen 2) have Fn key that "sudo libinput debug-events" sees as:

-event3   KEYBOARD_KEY                 +318.463s        KEY_WAKEUP (143) pressed

It can be assigned as a shortcut, leading to the action that the shortcut is bound to be launched whether Fn+something is used.

STEPS TO REPRODUCE
1. Have a thinkpad with Fn key.
2. Launch kcmshell6 keys and assign the key (it will register as "Wake Up") to for example "Launch KCalc", hit "Apply"
3. Try to change brightness with FN+F5/F6 (might vary  depending on your exact laptop model).

OBSERVED RESULT
Watch a multiplication of KCalc windows.

EXPECTED RESULT
Well, just the brightness is changed. Or it is impossible to assign Fn on its own as a shortcut (if that is the case, use rshould be informed as to why it is not possible).

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.9-201.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz
Memory: 64 GiB of RAM (62,5 GiB usable)
Graphics Processor 1: Intel® UHD Graphics 630
Graphics Processor 2: NVIDIA GeForce GTX 1650 with Max-Q Design
Manufacturer: LENOVO
Product Name: 20QVS0FP00
System Version: ThinkPad X1 Extreme 2nd

ADDITIONAL INFORMATION
I have been bitten by this when trying to assign a key not supported by Plasma as per https://bugs.kde.org/show_bug.cgi?id=500651