xdg-desktop-portal-wlr VS wayvnc

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

Yeah. On Wlroots or Sway, we can setup virtual displays pretty easily (swaymsg create_output, done). Then both the other person and yourself connect to the wayvnc vnc server server to see what's over there.

Available May 2020, https://github.com/any1/wayvnc/issues/7#issuecomment-6256611...

You can run remote applications with Wayland now: https://access.redhat.com/documentation/en-us/red_hat_enterp...

There is also a VNC server for fullscreen sessions (only supports wlroots compositors for now): https://github.com/any1/wayvnc

There's wayvnc.

It says on their GitHub page that "Gnome, KDE, and Weston are not supported". What does that mean?

I thought this existed in the form of wayvnc but from their README it seems they don't support the popular desktop environments (GNOME, KDE).

Not sure if I would call it hassle free, but wayvnc isn't that hard to set up.

And wayvnc

There is however a fresh issue on the wayvnc github with what looks like your problem. https://github.com/any1/wayvnc/issues/206

On wayvnc git master and sway 1.8 (or git master), you can script things so that a "virtual" display gets created automatically when someone connects to VNC, and removed when they disconnect.

See https://github.com/any1/wayvnc/pull/200/files

The script in the PR does something a bit different, but it's only an example and can be modified to do what I described in the first paragraph.

No - it's not X, it's doesn't share a screen in the way X does.

That said... if this is a shoddy attempt at a "gotcha" style question - Screen sharing and remote desktop are both supported.

Ex - for Gnome:

https://wiki.gnome.org/Projects/Mutter/RemoteDesktop

LibVNCServer for VNC support, FreeRDP for remote desktop protocol.

For KDE:

https://userbase.kde.org/Krfb

Which mostly just works as long as you have Pipewire and xdg-desktop-portal-kde installed (the base plasma-wayland session usually includes them)

This one is a bit less polished - some users still have problems with keyboard input, depending on the distro and other installed packages.

For Sway:

xdg-desktop-portal-wlr works just fine for screen sharing, and you can use https://github.com/any1/wayvnc for VNC access (including having a completely headless machine).