I recently upgraded from Debian 12 to Debian 13 (Trixie) and now using GNOME Shell 48.4 on Wayland.
Before the upgrade, I knew that many classic X11 utilities wouldn’t work on Wayland, but I was confident that there were Wayland-native alternatives.
However, after a clean install of Debian 13, I’ve discovered that the Wayland tools that are supposed to work are not working.
For example, I used to use:
- xdotool
- xrandr
- xprop
- wmctrl
- scrot
- maim (for sending screenshots to stdout) etc.
Wayland alternatives I expected to work (but don’t);
- wlrctl
- wtype
- grim
- grimshot
- flameshot
- ydotool (not in Debian 13 repos) etc.
The errors are as follows:
% grimshot copy area compositor doesn’t support zwlr_layer_shell_v1 % grim compositor doesn’t support wlr-screencopy-unstable-v1 % slurp compositor doesn’t support zwlr_layer_shell_v1 % wtype -M ctrl plus -m ctrl Compositor does not support the virtual keyboard protocol % wlrctl keyboard type “abc” Virtual Keyboard interface not found! I prefer to stay on Wayland if possible, since GNOME has made it increasingly difficult to use X11 and will likely drop support entirely by GNOME 50.
Does GNOME/Mutter intentionally not implement certain protocols (like virtual-keyboard, foreign-toplevel, etc.) that these tools depend on?
What are the official GNOME-supported ways to:
- Simulate keyboard/mouse input
- Capture screenshots to stdout (pipe to another process)
Is there a recommended developer-friendly path for scripting and automation under GNOME Wayland?
I really like Wayland’s design goals, but losing scripting and automation makes it very difficult for power users.
Any guidance on what currently works, and what the roadmap is for tools like wtype, wlrctl, or proper GNOME APIs for automation, would be hugely appreciated.