Comment by OsrsNeedsf2P
16 hours ago
I run Wayland but I'm not happy about it. Most autoclickers still don't work, and autotypers need sudo and group magic to get working.
16 hours ago
I run Wayland but I'm not happy about it. Most autoclickers still don't work, and autotypers need sudo and group magic to get working.
Root is definitely required to inject inputs at the kernel level using uinput, which I think is what you would hope, ignoring the fact that the typical Linux desktop still has a lot of other low hanging fruit to fix in terms of security.
Anyway though, the "standard" way to do automatic clicking and typing on Wayland is via the RemoteDesktop portal, named such because it is used with ScreenCast to support use cases like VNC and RDP servers. Despite the poor choice of name, it gives a general API for sending inputs programmatically.
https://docs.flatpak.org/en/latest/portal-api-reference.html...
This does require at least a one-time permission grant for an application to use, but at least on KDE it is possible for the permission to persist across runs.
I'm sure everyone is unenthused about having to deal with another way to do things, but it's at least decently straightforward... You could certainly invoke this from a quick Python script I reckon.
(There's also libei but it's kind of a mess imo and I don't know if it is well-supported yet.)
I get it's something you need but for the average user autotypers and clickers not working easily without permissions is a definite positive.
It's entirely the point of moving to Wayland for many.
https://github.com/atx/wtype seems to work for me with no special permissions. (On Sway; I won't comment on other compositors.)