this post was submitted on 04 Mar 2024
30 points (100.0% liked)

KDE

5407 readers
73 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
carlschwan@lemmy.kde.social
Bro666@lemmy.kde.social
herzenschein@pawb.social
Aniqakhokhar@lemmy.kde.social
30
How can I make F13-F24 to be actually recognized as F13-F24 in KDE Wayland? (lemmy.world)
submitted 9 months ago by sputge@lemmy.world to c/kde@lemmy.kde.social
17 comments fedilink hide all child comments
 

I got a big keyboard with F13-F24 keys. So here is the thing:

If you want to use e.g.: F22 as a shortcut in e.g.: Plasma settings it will get regonized as Touchpad On instead of as F22: https://imgur.com/a/GiyhBwD

The same goes for F13-F24:

F13 -> Tools
F14 -> Launch(7)
F20 -> Microphone Mute
F21 -> Touchpad Toggle
...

The shortcuts do work but the key name is just not correct.

I'd imagine that's because of the function keys on laptops..? But I am not using a laptop.

Anways one way to "fix" this in X11 was to create a .Xmodmap file:

keycode 191 = F13 F13 F13
keycode 192 = F14 F14 F14
[...]
keycode 202 = F24 F24 F24

and afterwars the system will regonize e.g.: F22 as F22: https://imgur.com/a/LB29wgo

A .Xmodmap file does not work in Wayland. What are my options here?

Thank you for your help.

PS: I found a simliar question here: https://discuss.kde.org/t/remapping-keys-such-as-f13/10275/3 but not answer.
I also found https://old.reddit.com/r/wayland/comments/x3tff6/adding_f13_f24_keys/kf36xa0/ but I want a real solution that works on the "user level" (like a .Xmodmap file in my home directory)...

top 17 comments
sorted by: hot top controversial new old
[–] D_Air1@lemmy.ml 4 points 9 months ago (1 children)

I don't know much about this kind of thing, but one thought that I had is that if you go to system settings -> keyboard -> keyboard. Is there any similar keyboard model that you can select that would essentially give you access to those keys?

[–] sputge@lemmy.world 3 points 9 months ago* (last edited 9 months ago) (1 children)

I have not found any... I guess I would need to select: "Generic | Generic 121-key PC" as the keyboard model, which does not exist.
This is the keyboard: https://github.com/bluepylons/Boston

But it's running QMK so one would have the same problem e.g.: with a 36-key keyboard which is programmed to send F13-F24 in some way...

[–] D_Air1@lemmy.ml 1 points 9 months ago

Sorry, not sure what else to do. I couldn't even find much information regarding a 121 key keyboard. I do wonder if there is a way to create a custom layout.

[–] Strit@lemmy.linuxuserspace.show 3 points 9 months ago (1 children)

Also, is your keyboard layout correct in Plasmas keyboard settings? eg, not just a 105 keys, but one with more keys?

[–] sputge@lemmy.world 1 points 9 months ago* (last edited 9 months ago)

I don't think that's possible since I have this issue with all my costume keyboards.
Some of them have only 36-keys. Such keyboard layouts do not exist in the Plasma keyboard settings.
They all use QMK as a firmware so I can program the keys to do anything I want.

[–] souperk@reddthat.com 3 points 9 months ago (2 children)

I cannot help, but your post got me wondering can you share your keyboard or a picture?

I cannot understand how some many fkeys could be useful. Why not use regural shortcuts?

[–] sputge@lemmy.world 6 points 9 months ago (2 children)
[–] HouseWolf@lemm.ee 6 points 9 months ago

Honestly that boards pretty slick! I was expecting some absolute unit like the Hyper 7

[–] souperk@reddthat.com 2 points 9 months ago

Boston is a compact battleship with a complement of 18 programmable keys, in a footprint 2u narrower than a full-size, and only about 1.5u wider than a 96%.

I am sold.

[–] UnRelatedBurner@sh.itjust.works 2 points 9 months ago

They are free macro keys

[–] pacjo@lemmy.dbzer0.com 2 points 9 months ago (1 children)

I had the same issue some time ago. I'll test it on plasma 6 and send it soon.

[–] pacjo@lemmy.dbzer0.com 4 points 9 months ago

Ok, It took some time by I finally found my writeup: https://github.com/agustinmista/positron/issues/15

... and on further inspection it's the same as you already posted. If it helps I can say it's been really stable, never breaking since I set it up (well apart from this week, but it's more of a I fucked up KDE and ignored all issues for the past few months, so a reinstall was necessary type of problem.

[–] Pantherina@feddit.de -2 points 9 months ago (1 children)

All the F keys are managed in your BIOS afaik

[–] Lenni@fosstodon.org 1 points 9 months ago* (last edited 9 months ago) (1 children)

@Pantherina @sputge I think the F[number] stuff gets directly passed to the OS, just the [Fn] stuff (those extra features to change the display brightness, volume, etc.) is managed by the Keyboard (?) or BIOS

[–] Pantherina@feddit.de 1 points 9 months ago (1 children)

Hm, so on my Thinkpad I had "sticky keys" which made the keys do the Fn function instead of the normal one, I had to change that in BIOS. But in KDE I can still assign F2=volUp (which is an OS feature and not the actually assigned Fn+F2 button)

[–] stepanzak@iusearchlinux.fyi 1 points 9 months ago (1 children)

On thinkpad, you can toggle it with Fn+Esc (FnLock)

[–] Pantherina@feddit.de 1 points 9 months ago

Yeah or disable in BIOS :D