⏱️ Lectura: 9 min
RustDesk has finally solved the problem holding Linux back in unattended remote desktop access: connecting to a Wayland session without anyone on the other end having to approve the connection. The feature even works from the login screen after a reboot, and supports multi-monitor setups.
📑 En este artículo
The announcement comes at a time when Wayland is already the default compositor in most modern distributions, but remote access support is still lagging behind: according to RustDesk, AnyDesk requires Xorg for incoming sessions on Linux, and TeamViewer describes its Wayland support as experimental.
TL;DR
- RustDesk published a preview build with unattended remote access for Wayland sessions on Linux.
- Support includes multi-monitor setups and connecting from the login screen after a reboot.
- For now, the preview only covers x86_64 systems based on Debian and Ubuntu.
- AnyDesk still requires Xorg for incoming sessions on Linux, according to RustDesk.
- TeamViewer describes its Wayland support as experimental on the most common desktop environments.
- RustDesk plans to bring unattended access to Fedora and Arch Linux before integrating it into the standard release.
- The project is asking the community for real-world testing, especially on multi-monitor setups.
Introduction
For any developer managing Linux desktop servers, or providing remote support to colleagues on modern distros, the migration to Wayland brought a practical problem: most remote access tools were still tied to X11 (Xorg), the windowing system Wayland aims to replace. RustDesk, the open source alternative to TeamViewer and AnyDesk, just took a step that closes much of that gap.
The project is known in the community precisely for offering the same kind of features as proprietary tools, but with auditable code and the ability to self-host the entire server. Adding unattended access on Wayland puts it, at least on this specific point, one step ahead of its commercial competitors.
What happened
The RustDesk team released a separate preview build, currently available only for x86_64 systems based on Debian and Ubuntu, that adds native unattended remote access over Wayland. According to the official announcement, once the initial setup is complete, it’s possible to connect to the remote machine even when no one is present, including from the login screen after a reboot.
The build also supports multi-monitor setups, which tends to be the first point of failure in early implementations of remote access over Wayland, where each compositor exposes screens differently to the capture protocol. RustDesk also published a demo video on X showing the complete flow, from connection to an active session with no human intervention on the remote end.
Context and history: why Wayland was a problem
Wayland has spent over a decade as the candidate protocol to replace X11, but only in recent years have the major distros (Fedora, Ubuntu, and later Arch derivatives) made it the default compositor. The change fixed security and architecture problems that X11 had carried since the eighties, but it broke an assumption many remote desktop tools took for granted: that any process with access to the graphical session can read the full framebuffer and simulate keyboard and mouse events without asking permission.
Wayland inverted that model by design. Each compositor decides what an external client can capture, typically through xdg-desktop-portal, and by default requires explicit on-screen user approval before sharing video or injecting input. It’s a genuine security improvement, but a problem for the unattended access use case, which is exactly what a sysadmin needs when connecting to a graphical server at three in the morning with nobody sitting in front of it.
That’s why, according to RustDesk’s own announcement, AnyDesk still requires Xorg to receive incoming sessions on Linux, and TeamViewer keeps its Wayland support classified as experimental for the most common desktop environments, like GNOME and KDE Plasma.
Technical details: how RustDesk works on Wayland
At a technical level, the Wayland challenge for remote desktop comes down to two pieces: screen capture and input event injection. In X11 both were trivial because the X server exposed global APIs without asking permission. In Wayland, each compositor (Mutter on GNOME, KWin on KDE, Sway) implements its own portal backend, and that’s usually where behavioral differences between distros show up.
To achieve unattended access, without an approval dialog on every session, RustDesk needs the authorization step to be resolved once during initial setup, with the session enabled even before a user is logged in, that is, from the login screen (typically GDM or SDDM). That means running a component as a system service with permissions to capture the screen and inject input, not just as a process in the logged-in user’s session.
💭 Key point: the real leap in this build isn’t supporting Wayland (several tools already render on Wayland), it’s supporting it with no human present, which is the scenario a sysadmin or a remote support team actually needs.
Getting started: trying the preview build
The unattended Wayland build is, for now, a package separate from stable RustDesk, meant for testing. Here’s how to install it on the three main platforms: the client runs on any of the three, while the unattended-access preview build is specific to the Linux x86_64 Debian/Ubuntu host.
# Linux (Debian/Ubuntu x86_64): preview build with Wayland support
wget https://github.com/rustdesk/rustdesk/releases/latest/download/rustdesk-wayland-preview.deb
sudo apt install ./rustdesk-wayland-preview.deb
rustdesk --version# macOS (client, via Homebrew)
brew install --cask rustdesk
# Windows (client, via winget)
winget install --id RustDesk.RustDeskAfter installing, each machine receives an ID and a temporary password generated locally. To finish setting up unattended access, you need to set a permanent password from the client (Security menu) and, if you’re going to self-host the server instead of using the public relay, point the client to your own rendezvous server:
# Point the client to a self-hosted server
rustdesk --config network.custom-rendezvous-server 203.0.113.10:21116To confirm the host is truly unattended, the simplest test is to log out or reboot the remote machine and connect from another device pointing to the same ID: if the session connects directly to the login screen without asking for approval on the remote end, the setup is correct. You can also check the service status on the host:
# Check that the unattended access service is active
systemctl status rustdesk
journalctl -u rustdesk -n 50 --no-pagerImpact and analysis
The announcement matters less as a new feature and more for what it says about the state of remote access on Linux in general: it’s still the weakest link compared to Windows and macOS, where unattended access has been standard for years. For teams that already migrated their workstations or graphical servers to Wayland (Fedora Workstation, Ubuntu 22.04 onward, most new KDE Plasma installations), the alternative until now was forcing an Xorg session just to provide remote support, which runs counter to the reason they migrated to Wayland in the first place.
RustDesk vs. AnyDesk vs. TeamViewer on Wayland
| Tool | Wayland status (Linux) | Unattended access | License |
|---|---|---|---|
| RustDesk (preview build) | Supported, in preview for x86_64 Debian/Ubuntu | Yes, even from the login screen | Open source (AGPL-3.0) |
| AnyDesk | Requires Xorg for incoming sessions | Yes, but only on Xorg | Proprietary |
| TeamViewer | Experimental on common desktop environments | Limited | Proprietary |
Licensing also weighs into the comparison: RustDesk is open source, which allows self-hosting the entire server (rendezvous and relay) and auditing the code that runs with elevated permissions on the remote machine, something neither AnyDesk nor TeamViewer offers.
The following diagram summarizes the flow between the client, the rendezvous server, and the Linux host running Wayland, including the portal layer that mediates access to the screen and input:
flowchart TD
A["RustDesk Client"] --> B["Rendezvous Server"]
B --> C["Linux Host with Wayland"]
C --> D["xdg-desktop-portal"]
D --> E["Compositor (Mutter, KWin, Sway)"]
subgraph Remote Host
C
D
E
endThe client never talks directly to the compositor: everything goes through the portal, which is precisely the piece RustDesk had to learn to operate without relying on manual approval for every connection.
⚠️ Heads up: the unattended Wayland build is a preview, separate from stable RustDesk, and for now only covers x86_64 Debian/Ubuntu. If your fleet runs Fedora, Arch, or ARM architecture, there’s no official build yet: you’ll have to wait for the team to stabilize it and bring it into the standard release.
What’s next
According to the announcement, the plan is to add more distributions, Fedora and Arch Linux are explicitly mentioned, before merging this feature into RustDesk’s standard release. The team is asking for community testing, particularly on multi-monitor setups, which is the scenario where bugs in this kind of integration tend to show up most.
For anyone managing Linux desktop infrastructure who has been postponing the migration to Wayland for this specific reason, this preview is the first concrete sign that the gap with Windows and macOS is closing.
Try it yourself: download the preview build from RustDesk’s official blog and test an unattended session on your own Wayland machine today.
📖 Summary on Telegram: View summary
Frequently Asked Questions
Is RustDesk on Wayland already in the stable release?
No. For now it’s a separate preview build, available only for x86_64 Debian/Ubuntu systems.
Does it work with multiple monitors?
Yes, the announcement confirms support for multi-monitor setups in this preview.
Can I use it from the login screen?
Yes, that’s precisely the core use case: connecting even when nobody is logged in, including after a reboot.
Which distros will be added next?
RustDesk mentioned Fedora and Arch Linux as the next targets, before integrating the feature into the standard release.
Is it free and open source?
Yes, RustDesk is an open source project and can be self-hosted; it also offers a managed server for those who don’t want to run their own.
Does it replace the stable version of RustDesk?
No, it’s a separate package meant for testing while the team gathers feedback before merging it into the main product.
References
- RustDesk Blog: official announcement of the unattended Wayland access preview build.
- RustDesk on GitHub: source code for the client and server.
- Wayland (freedesktop.org): official Wayland protocol documentation.
- Wikipedia: Wayland: historical context of the protocol versus X11.
📱 Like this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day. @programacion
Imagen destacada: Foto de Roman Synkevych en Unsplash
0 Comments