For decades, remote desktop was simple because the OS didn't care who was looking at the pixels. Wayland, increased security sandboxing, and headless GPU power management are all good things for security and efficiency. But they break the old model of screen scraping.
Instead, you get a grey box. A cold, mechanical error stares back at you: .
For thirty years, X11 (X Window System) ruled the roost. It was insecure, messy, and old—but it was permissive . Any application could read the pixels of any other window. Remote desktop tools loved X11 because it was like an open book. anydesk display_server_not_supported
Enter Wayland. Wayland was built for security and smooth rendering. Each application is a fortress. One application cannot see the pixels of another unless explicitly allowed.
The days of assuming you can always grab the framebuffer are ending. Until the remote desktop tools catch up (Rustdesk, for example, handles Wayland better), you have two choices: downgrade your security (X11) or trick your hardware (dummy plugs). For decades, remote desktop was simple because the
The operating system reads it as: "The protocol used to draw the windows is incompatible with the capture method."
AnyDesk isn't crashing. It’s looking at your graphics stack and saying, "I don't speak that dialect." If you are on Linux, 99% of the time, this error is due to Wayland . Instead, you get a grey box
export ANYDESK_USE_WAYLAND=0 anydesk If that fails, switch your login session to "Ubuntu on Xorg" (or your distro’s X11 fallback) from the login screen. This isn't a hack; it’s a temporary truce. The second most common culprit is the headless server . You’re trying to remote into a machine that has no physical monitor plugged in.