Created attachment 166432 [details] Example: F23 gets recognized as "Touchpad Off" SUMMARY *** I have a macropad (running QMK Firmware) which is able to produce key codes such as F13 - F24. When trying to assign shortcuts in the System Settings e.g.: F23 will get recognized as "Touchpad Off" or F13 as "Launch (9)". I'd expect the system to show F23 as the shortcut button when I assign F23 as the shortcut - and not "Touchpad Off". The System settings shortcuts do work but the F13 - F24 keys don't get recognized in all applications - not even "wrongly" as e.g.: "Touchpad Off". *** STEPS TO REPRODUCE 1. Have a keyboard/macropad where you know for sure that it's able to produce the key codes for F13-F24. 2. Try to assign a key - that sends F13, F14 etc. - to a shortcut in the System Settings. OBSERVED RESULT The populated key under Custom shortcuts will not show F13 - F24 but things like "Launch (9)", "Launch (A)", "Touchpad Off" etc. EXPECTED RESULT The populated key under Custom shortcuts shows e.g.: F13 since I pressed F13 on my macropad. ___ In the shortcut System settings this is only a "visual bug" (I can use the shortcut) but e.g.: I can't use F22 at all in my music-player DeaDBeef - only after creating the .Xmodmap described in ADDITIONAL INFORMATION. Plasma's correct handling of F13 - F24 is thus also needed for user applications. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION On X11 I was able to "fix" this by using a .Xmodmap file containing: keycode 191 = F13 F13 F13 keycode 192 = F14 F14 F14 [...] keycode 202 = F24 F24 F24 This made F13-F24 be recognized as such by the system. But this does not work under KDE Wayland.
EDIT: I can confirm this bug on Arch Linux/KDE Plasma 5.27.10 & on KDE Neon 6.0 I also forgot to mention that I can't assign F24, F21 and F19 AT ALL - not even "wrongly" but this got already reported in https://bugs.kde.org/show_bug.cgi?id=422401 I guess.
What is the output of `xmodmap -pke`? Do you see F13-F24 in there?
(In reply to fanzhuyifan from comment #2) > What is the output of `xmodmap -pke`? Do you see F13-F24 in there? Thank you for your reply! No, I see: ``` [...] keycode 191 = XF86Tools NoSymbol XF86Tools keycode 192 = XF86Launch5 NoSymbol XF86Launch5 keycode 193 = XF86Launch6 NoSymbol XF86Launch6 keycode 194 = XF86Launch7 NoSymbol XF86Launch7 keycode 195 = XF86Launch8 NoSymbol XF86Launch8 keycode 196 = XF86Launch9 NoSymbol XF86Launch9 keycode 197 = keycode 198 = XF86AudioMicMute NoSymbol XF86AudioMicMute keycode 199 = XF86TouchpadToggle NoSymbol XF86TouchpadToggle keycode 200 = XF86TouchpadOn NoSymbol XF86TouchpadOn keycode 201 = XF86TouchpadOff NoSymbol XF86TouchpadOff keycode 202 = [...] ``` So this would "explain" why Plasma thinks that e.g.: F23 => keycode 201 => "TouchpadOff" I guess..? And also why keycode 197 (F19) & keycode 202 (F24) are not being registered at all - because they are empty. ___ If I use my .Xmodmap file (for example:) keycode 200 = F22 F22 F22 The output of `xmodmap -pke` obviously changes to ``` [...] keycode 200 = F22 F22 F22` [...] ``` as well (at least in X11 - NOT in wayland) ___ I'd suggest that this should be changed to F13-F24... It's frustrating that Plasma seems to just assume that everyone is using a laptop and assigns things like XF86TouchpadOn, XF86TouchpadOff etc. instead of F13-F24.
(In reply to Moritz from comment #3) > I'd suggest that this should be changed to F13-F24... It's frustrating that > Plasma seems to just assume that everyone is using a laptop and assigns > things like XF86TouchpadOn, XF86TouchpadOff etc. instead of F13-F24. I don't think plasma is responsible for setting the keymap, so I am calling this closed-downstream for now. Adding support for keys not in the keymap is covered in BUG 422401.