wayvnc VS input-leap

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

Ah right, looks like the VNC server you're using is xorg only. You can try WayVNC for gaming mode https://github.com/any1/wayvnc .

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.

I'm already using waynergy with input-leap as my main way to control the laptop when it is docked. It is amazing.