kanshi VS wayvnc

Without digging into you problem, i just let you know one options/tool as an addition: https://github.com/emersion/kanshi

This works, but after a reload of the config the configuration is gone. Then I found this discussion and changed the line to:

Kanshi is not exactly what you're looking for but i stumbled across this when I was writing the dynamic display configuration page.

You should use different scale factors on each monitor. You can do it in your sway configuration, or use something like kanshi that automatically applies different settings based on what is connected.

If this fixes your problem you'll want to apply this fix: Disable Laptop screen upon closing screen. or you can use something like Automatic display profile switcher when you connect your external display to switch it to while also disabling your laptop screen.

I also heard of kanshi for monitor configuration, but I believe there's an open bug where sway reload breaks kanshi config... which kind of defeats the purpose.

kanshi should be able to do it.

Assuming your connected monitors may change - you plug another one in and then you want to move workspaces the new output: kanshi can help you with that. You can tell kanshi to execute commands when it matches a profile.

For this you can use kanshi.

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).