You are not logged in.

#1 2025-12-10 08:56:25

Smoerrebroed
Member
From: Germany
Registered: 2011-07-24
Posts: 115

Solaar: Cannot trigger custom keypresses

With regard to this thread https://bbs.archlinux.org/post.php?tid=310060 I seem to be running into related but different issues:

So I just got my shiny new Logitech MX Master 4 (because my MX Master 3 started disintegrating after so many years), and for some odd reason, some of the detault button actions have changed. So while I didn't have to do anything previously, now I need to use Solaar in order to setup some custom key remapping.

After doing so and setting up my Solaar rules the way I think I need to, I'm seeing:

2025-12-10 08:58:40,104,104     INFO [MainThread] logitech_receiver.diversion: KeyPress action: ['Super_L', 'Tab'] release, group 0, modifiers 16
2025-12-10 08:58:40,105,105  WARNING [MainThread] logitech_receiver.diversion: cannot create uinput device: "/dev/uinput" cannot be opened for writing
2025-12-10 08:58:40,105,105  WARNING [MainThread] logitech_receiver.diversion: no way to simulate key input

Which makes sense:

$ ls -la /dev/uinput 
crw------- 1 root root 10, 223 10. Dez 07:21 /dev/uinput

I have reloaded the rules, issued a trigger, and even rebooted, but somehow the uinput device isn't accessible by anybody other than root. Any idea what might be missing? I'm using the Logi Bolt USB-C receiver that came with the mouse, and it does show the correct vendor attribute to be picked up by the rule. Any ideas why it might not work as expected?

FWIW, changing permissions to 606 on /dev/uinput fixes this - but of course those get reset with the next reboot.

PS: This is on Wayland, but generally speaking that should be supported, right?

Last edited by Smoerrebroed (2025-12-10 09:13:57)

Offline

Board footer

Powered by FluxBB