xdg-desktop-portal-wlr VS wlroots

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

Even then, "tinywl" which aims to be a "minimum viable product" Wayland compositor based on wlroots is almost 1k lines:

https://github.com/swaywm/wlroots/tree/master/tinywl

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.