KasmVNC VS wayvnc

Not exactly the same thing, but I had good experience with KasmVNC.

Despite having VNC in its name, it isn't fully compliant with the VNC protocol and doesn't support regular VNC clients. Instead, it exposes a web client that you can access to connect to the machine. It also felt surprisingly snappy and nice to use compared to my previous experiences with regular VNC.

https://github.com/kasmtech/KasmVNC

This may help: https://github.com/kasmtech/KasmVNC/issues/124

KasmVNC is a standalone project that gets embedded into the above images. https://github.com/kasmtech/KasmVNC

- KasmVNC is a standalone open source project that powers the container steaming portion of workspaces - meaning the rendering of the container GUI environment and the keyboard/mouse interaction. KasmVNC can be used in containers, VMs or hardware. It is GPL2. https://github.com/kasmtech/KasmVNC

KasmVNC Details kasmvncserver_jammy_1.1.0_amd64.deb

The rendering for container sessions is powered by our independent open-source project KasmVNC . Here is a video on some of the improvements to the streaming tech we've made in recent months. It shows an example of how performant it can be

** Tutorial: ** https://medium.com/@matthew.mcclaskey/docker-container-ui-streaming-doom-2b8e453a23a6 ** Kasmvnc: ** https://github.com/kasmtech/kasmvnc

- https://github.com/kasmtech/KasmVNC

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 .