MaxGyver83

joined 2 years ago
[โ€“] MaxGyver83@feddit.de 3 points 2 years ago (1 children)

This fixes it. Thank you! Do you know why I need TAG+="uaccess" now but didn't need it in the past?

[โ€“] MaxGyver83@feddit.de 1 points 2 years ago* (last edited 2 years ago) (3 children)

I have tried this but the problem persists after a reboot.

UPDATE: I have tested this again. I forgot to mention that it's even worse with an /etc/modules-load.d/uinput.conf. After a reboot, I get the same error as before but a sudo modprobe uinput doesn't help anymore. I have to run sudo modprobe -r uinput; sudo modprobe uinput to fix the openFd: permission denied error (temporarily).

 

I use dwm on Arch and in my autostart.sh I start KMonad. This requires me to be member in the uinput group (what I am). Since a few days starting KMonad fails with:

kmonad: /dev/uinput: openFd: permission denied (Permission denied)

(Same when I try to start it manually.)

The workaround is to run sudo modprobe uinput and then to start kmonad (again).

I just don't understand why this is necessary now. I have this udev rule defined:

/etc/udev/rules.d/90-kmonad.rules:

KERNEL=="uinput", MODE="0660", GROUP="uinput", OPTIONS+="static_node=uinput"

I guess this broke because of a sudo pacman -Syu. Has anything changed in the last few days? I can't find anything that looks related on Arch Linux.