sputge

joined 1 year ago
sorted by: new top controversial old
How can I make F13-F24 to be actually recognized as F13-F24 in KDE Wayland? in c/kde@lemmy.kde.social
[–] sputge@lemmy.world 1 points 8 months ago* (last edited 8 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.

How can I make F13-F24 to be actually recognized as F13-F24 in KDE Wayland? in c/kde@lemmy.kde.social
[–] sputge@lemmy.world 3 points 8 months ago* (last edited 8 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...

How can I make F13-F24 to be actually recognized as F13-F24 in KDE Wayland? in c/kde@lemmy.kde.social
30
How can I make F13-F24 to be actually recognized as F13-F24 in KDE Wayland? (lemmy.world)
 

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)...

Why has nobody ever heard of Distrobox? Let me tell you why everyone should take a look at it! in c/linux@lemmy.ml
[–] sputge@lemmy.world 4 points 9 months ago* (last edited 9 months ago) (3 children)

e.g.: Duplicacy Web Edition is missing on the Nix side of things.
It does exist on the AUR: https://aur.archlinux.org/packages/duplicacy-web
This keeps me from switching to NixOS :(.

Bluetooth dongle recommendation in c/linux@lemmy.ml
[–] sputge@lemmy.world 6 points 11 months ago* (last edited 11 months ago) (1 children)

https://medium.com/codex/bluetooth-5-on-linux-overview-of-kernel-supported-dongles-and-chipsets-c6f2b632b236

(At the bottom of the text is also a link to a Reddit discussion about this subject)

I bookmarked this article a while ago.

Just learned about AppImageLauncher in c/linux@lemmy.ml
[–] sputge@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 children)

According to the uninstall instructions here: https://github.com/probonopd/go-appimage/blob/master/src/appimaged/README.md#initial-setup

appimaged should create the everything itself in order for auto start to work.

e.g. systemctl --user status appimaged.service says that the service is enabled for me.

I would follow the installation instructions and if that does not work, the uninstall instructions in reverse to create the service yourself (probably with systemctl --user enable --now appimaged.service)

Just learned about AppImageLauncher in c/linux@lemmy.ml
[–] sputge@lemmy.world 16 points 1 year ago* (last edited 1 year ago) (3 children)

AppImageLauncher caused me problems in the past, similar to in this post.

So I switched to appimaged and have never looked back.

An implementation of AppImage tools written in Go by the inventor of the AppImage format.

After uninstalling AppImageLauncher, I had to make sure that ~/.config/systemd/user/default.target.wants/appimagelauncherd.service was also removed!

BTW the last release of AppImageLauncher is from 2020!