input-remapper VS kbct

I got my G29 working, but I am using a T-LCM which isn't correctly recognized. I installed Input Remapper but it's not recognized.

Perhaps GitHub - sezanzeb/input-remapper: 🎮 ⌨ An easy to use tool to change the behaviour of your input devices. will do?

OK, I will byte, have you tried Input Remapper[1] ?

I think most of your problem is coming from using Rocky Linux, it is much easier to find support on Ubuntu derivatives for tools made by the community in general.

[1] https://github.com/sezanzeb/input-remapper

- Input Remapper: Custom hotkeys & remapping of keys (with Wayland support)

Then you can use something like input-remapper to do whatever you want.

Ask upstream?

However I want my system to be automatically remapped at boot. Input Remapper installs a systemd service by default and I found that someone wrote an OpenRC init script for it, so I created a file called input-remapper in etc/init.d, copied the text of the script into it, saved it, then used chmod +x on it, so it has the same attributes as other init scripts.

I had a similar problem with the Tecurs KB510 I got at work. The only way I found to type F1-F12 keys on Linux was to set up a hack with kbct [0] and the Super key... until I tried the configuration described in the gist you linked. Thanks a lot for that !

[0] https://github.com/samvel1024/kbct

I use KBCT and encourage others to support it: https://github.com/samvel1024/kbct

kbct

>Creating a "standardized experience" like Windows usually means that configurability goes right out the window. It's how you get abominations like dconf or the GNOME music player

I don't understand how you connected these dots and I'd suggest against calling things abominations. You don't have to use dconf or the GNOME music player, those aren't standardized. If someone does like them I think they're perfectly fine, they do exactly what they're advertised to do. It's also fine if you don't like them, they're just two options from the many configuration databases and media players that you can choose from.

>But why shouldn't I be able to run xbindkeys or sxhkd or whatever hotkey dameon I want?

In some ways you actually can but it depends on the hotkey daemon and how it's implemented. The reason for that is technical, those are implemented with X grabs which have a number of usability and security issues. There are a few key rebinding daemons that use evdev directly so they work with Wayland:

https://github.com/samvel1024/kbct

https://github.com/snyball/Hawck

But these also do have similar security issues to X key grabs, in that they effectively operate as keyloggers. If you're looking for an API that works purely within Wayland and lets unprivileged clients request key rebinding, that doesn't exist yet. Somebody would need to specify what that API looks like and figure out a good way to make it secure. What would the end goal of the API be, and how could the system (and by extension, the user) tell the difference between a legitimate hotkey daemon and a malicious keylogger? And would it actually be any better than the approach of snooping evdev? I don't know the answer to these questions but you may have more experience with this than I do.