xdg-desktop-portal-wlr VS ydotool

It comes with a systemd service file https://github.com/emersion/xdg-desktop-portal-wlr/blob/master/contrib/systemd/xdg-desktop-portal-wlr.service.in that you can use

Are you running the Wayland envvar for Firefox, MOZ_ENABLE_WAYLAND=1? Because the rest of your setup sounds very similar to my (working) setup. You could also run the Python test script included with xdg-desktop-portal-wlr (bottom of this page) as a sanity check that nothing's going wrong there

- Global hotkey portal

Not yet: https://github.com/emersion/xdg-desktop-portal-wlr/issues/107

You'll need this

I believe that a lot of the current approach to fixing it is something similar to xdg-desktop-portal. That's for signaling for screenshots, but a similar idea could work for listening for key events without being focused, apparently. It bypasses the standard Wayland system completely and uses D-Bus and Pipewire instead. I'm not too familiar with the details myself, though.

I don't know which of the xdg-desktop-portal backends you would need for gamescope, but xdg-desktop-portal-wlr has a config file which it reads where you can set the preferred output and set the chooser_type to none. That makes it skip the screen selector for me.

See these links for more info: * flameshot: flameshot gui from cli does nothing. dbus error UnknownMethod: "No such interface “org.freedesktop.portal.Screenshot” #2872 * xdg-desktop-portal: No such interface “org.freedesktop.portal.Screenshot” on object at path /org/freedesktop/portal/desktop #861 * xdg-desktop-portal-wlr: screenshot: Announce version property

This is a known issue: https://github.com/emersion/xdg-desktop-portal-wlr/issues/83

Wayland provides little by design, so this is quite typical. For example:

Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.

They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.

Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.

[0] https://superuser.com/questions/1221333/screensharing-under-...

[1] https://unix.stackexchange.com/questions/292868/how-to-custo...

[2] https://github.com/ReimuNotMoe/ydotool

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.

For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.