ReimuNotMoe / ydotool

Generic command-line automation tool (no X!)
GNU Affero General Public License v3.0
1.36k stars 77 forks source link

failed to open uinput device: No such device #234

Open gmankab opened 3 months ago

gmankab commented 3 months ago

Apr 02 07:17:08 fedora systemd[1]: Started ydotool.service - Starts ydotoold service. Apr 02 07:17:08 fedora ydotoold[190083]: failed to open uinput device: No such device Apr 02 07:17:08 fedora systemd[1]: ydotool.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Apr 02 07:17:08 fedora systemd[1]: ydotool.service: Failed with result 'exit-code'.

os: fedora silverblue compositor: hyprland installed via rpm-ostree ydotool is also installed via rpm-ostree

gmankab commented 3 months ago

tested on gnome which is preinstalled on fedora silverblue, same issue

corubba commented 2 months ago

I ran into this because the user didn't have read+write permissions on /dev/uinput. I only needed it for a quick one-off use, so went with sudo chmod a+rw /dev/uinput to fix it. As a long term solution, you are better of with a udev rule that assigns a group and grants read+write to that group (instead of everybody like with that chmod).

gmankab commented 2 months ago

thanks

Paiusco commented 2 months ago

@ReimuNotMoe maybe this can be fixed somehow? Or add a check if this is the case on /dev/uinput we can at least let the user know what to do?

What do you think would be a good approach?