[kde] [Bug 482480] Key Codes F13 - F24 don't get handled as expected in KDE Plasma

[Moritz]

https://bugs.kde.org/show_bug.cgi?id=482480

--- Comment #3 from Moritz <moritz1000 at googlemail.com> ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.