Start by matching your compositor and session needs.
Why does the capture method matter?
X11 console-sharing VNC servers used the root window for desktop capture. X.Org X11R7.7 protocol specification, GetImage (2012).
WayVNC 0.8.0 targets wlroots-based Wayland compositors; its README excludes GNOME, KDE, and Weston. WayVNC 0.8.0 README.
Start with the compositor family, whether the user is already logged in, and whether the target is the attached session or a new virtual session.
Record before choosing
| Environment and version | Protocol and scope |
|---|---|
| wlroots-based compositor with WayVNC 0.8.0 | VNC. Match the compositor to WayVNC’s output-management, screencopy, and virtual-input requirements. WayVNC 0.8.0 protocol definitions; WayVNC 0.8.0 README. |
| GNOME Remote Desktop 46.5 | VNC backend documented in the GNOME Remote Desktop 46.5 grdctl manual. |
| KDE Plasma 6.1 remote desktop | System Settings remote desktop was introduced in Plasma 6.1 (KDE Plasma 6.1 release announcement). KRdp v6.1.0 uses RDP (KRdp v6.1.0 README). |
| Raspberry Pi OS Trixie | VNC through the Wayland path in raspi-config (Raspberry Pi raspi-config, Trixie branch). Release scope: Raspberry Pi, Trixie: the new version of Raspberry Pi OS. See the Raspberry Pi setup guide for that separate task. |
| TigerVNC 1.16.0 on a wlroots-based compositor or one implementing the RemoteDesktop portal | VNC desktop sharing through w0vncserver (TigerVNC 1.16.0 w0vncserver manual). |
WayVNC 0.8.0 needs a running Wayland session and WAYLAND_DISPLAY set for that session. WayVNC 0.8.0 FAQ. Run the check below as the graphical user running WayVNC.
For GNOME Remote Desktop 46.5, the GNOME Remote Desktop 46.5 grdctl manual documents a VNC backend and a status query. The checks below inspect an existing configuration.
For Raspberry Pi configuration, use the Raspberry Pi setup guide.
Choose the check for your installed version. Run it in a terminal as the graphical user who owns that configuration.
For an already-running WayVNC 0.8.0 instance:
wayvncctl version
Expected result: JSON reporting the running instance and dependency versions. WayVNC 0.8.0 wayvncctl manual.
For an existing GNOME Remote Desktop 46.5 configuration:
grdctl status
Expected result: the current remote-desktop status. GNOME Remote Desktop 46.5 grdctl manual. Record the reported status before changing the configuration.
If either command fails or the expected output is missing, stop and record the command output and installed version for your support request.
The portal model
In xdg-desktop-portal 1.20.0, input-device selection uses SelectDevices(); screen-capture negotiation uses SelectSources() and OpenPipeWireRemote(). The latter opens access to the PipeWire remote containing the screen-cast streams. xdg-desktop-portal 1.20.0 RemoteDesktop interface; xdg-desktop-portal 1.20.0 ScreenCast interface.
Confirm the protocol your viewer needs before choosing a server.
Which session do you need?
If you need to share an existing wlroots-based desktop through VNC, consider WayVNC 0.8.0 only after matching its compositor requirements (WayVNC 0.8.0 README; WayVNC 0.8.0 protocol definitions). TigerVNC 1.16.0 offers VNC sharing for a wlroots-based compositor or one implementing the RemoteDesktop portal (TigerVNC 1.16.0 w0vncserver manual). KDE’s KRdp v6.1.0 uses RDP (KRdp v6.1.0 README).
Test whether consent is required after every login and what the remote user sees when the screen locks.
For headless planning, GNOME Remote Desktop 46.5 has a separate gnome-remote-desktop-headless.service; it conflicts with gnome-remote-desktop.service (GNOME Remote Desktop 46.5 headless service unit).
Verify encryption, authentication, lock-screen behavior, and what happens after reboot.
What should you test on your setup?
Include your clipboard, monitor-layout and scaling requirements when evaluating a setup. Record the clipboard direction and data types you need, and test input placement on each display.
Record what the remote user can see and control when the session locks or a privilege prompt appears.
Record the distribution, desktop, compositor, and package versions in operational notes. Recheck the desktop’s supported route after major upgrades.
Discuss this in the community
Sources accurate as of 30 September 2026.
Open-source VNC suits personal projects and home labs. When your business depends on remote access, RealVNC Connect adds end-to-end encryption, centralised management and commercial support from the team that created VNC.