Skip to main content

Linux Remote Control

Which display servers and desktop environments support remote control, what the agent sets up on the device, and Linux-specific session behaviors.

Introduction

Remote control on Linux works the same way it does on Windows and macOS: click the OS icon next to an online device and a live remote session opens in a new browser tab. The session is end-to-end encrypted and connects peer-to-peer when network conditions allow.
​

What's different on Linux is what's underneath. Linux desktops vary in display server (X11 or Wayland) and desktop environment. Level can use a supported graphical session or capture an available display directly, including a text-only console. This article covers what's supported, what the agent sets up on the device, and the behaviors specific to Linux sessions.
​

For session controls, toolbars, and clipboard tools, see Remote Control. Clipboard availability depends on the session type.


⚙️ PREREQUISITES

  • The Level agent is installed, up to date, and online on the target device

  • Your account has remote control permission for the device's group

  • A display Level can capture, through a supported graphical session or direct display capture. A graphical desktop is not always required.

  • For GNOME's compositor capture path: PipeWire and a running D-Bus session bus. KDE's compositor capture path also uses PipeWire. Direct KMS or framebuffer capture uses a separate path.


What's Supported

Remote control availability depends on the device's session, display, and capture method rather than its distribution name. Check these requirements:

  1. The Level Linux agent runs on it.

  2. It has a supported graphical session or a display available for direct capture (see below).

  3. The services and components needed by the selected capture method are available. GNOME's compositor capture uses PipeWire and the session D-Bus APIs; KDE's compositor capture also uses PipeWire.

A desktop environment's name alone does not guarantee capture on every version, graphics driver, or display configuration.

Display Servers

Both major Linux display servers are supported. For graphical sessions, the agent detects what's running and picks the capture path automatically. Wayland is tried first, with X11 as the fallback. Eligible sessions can also use direct KMS capture when compositor capture is unavailable or fails during startup.

Wayland is supported on these desktop environments:

  • GNOME (Mutter)

  • KDE Plasma (KWin)

  • COSMIC (System76 / Pop!_OS)

  • wlroots-based compositors such as Sway and Hyprland

X11 / Xorg is supported under any desktop environment. XFCE, MATE, Cinnamon, and older GNOME or KDE sessions running on Xorg all use this path.

ℹ️ NOTE: GNOME, KDE, COSMIC, Sway, and Hyprland are tested environments. Other Wayland compositors may work through their capture protocols or an eligible direct-display fallback, but neither path guarantees support for every compositor or hardware configuration. If Level cannot capture a display, use background management while you check the session and display configuration.

Architectures

Both x86-64 and ARM64 devices are supported.


A Capturable Display Is Required

For graphical sessions, Level follows session changes automatically. If a user logs in, out, or switches accounts during a session, Level re-attaches to the new session. It prefers an eligible active desktop session on the primary seat (seat0). If none is available, it can select an active X11 user session without a seat, provided the session has a non-empty display. This can include an xrdp session in a container; it is not a guarantee that every xrdp or container setup will connect.

💡 TIP: If a Linux device has no display Level can capture, use background management. Terminal, File Explorer, Processes, and Services all work without a graphical session. See Device Manage.

You don't need a user logged in. A supported graphical login screen or a capturable text-only console can be a remote-control target. Login-screen availability still depends on the greeter's display and capture path.
​

When no eligible graphical session is available, the agent tries direct kernel capture. A text-only boot, a stopped display manager, or a tty/getty login no longer rules out remote control by itself:

  • KMS capture: reads an active display exposed by the Linux graphics subsystem.

  • Framebuffer capture: provides a fallback when no active KMS display is available and a supported framebuffer device exposes the text console. It is not used as a desktop-compositor fallback.

  • Desktop fallback: eligible graphical sessions on seat0 can fall back to KMS when the compositor cannot supply a stream. KMS and kernel input fallbacks are not added to seatless X11 sessions, so they do not capture or control a different seat's display.

  • No capturable display: a serial-only server or VM with neither a capturable graphical session nor a supported display device still needs background management. Console capture does not make every headless configuration remotely viewable.

🖥️ PLATFORM NOTE: On older GNOME releases, the login screen and user session may use different display servers and capture APIs. Current agents include older-GNOME compatibility paths and direct-display fallbacks, but a working user session does not establish that every greeter or lock screen on the same release will work. Check the actual login-screen session rather than relying on the GNOME version alone.


What the Agent Sets Up

On most systems, remote control works with no manual setup. On GNOME and KDE, the agent installs a small component to enable Wayland session capture and input.

GNOME

The agent automatically installs a Level GNOME Shell extension for the logged-in user. It selects the right extension build for the installed GNOME Shell version, so a wide range of GNOME releases is handled without any action on your part.
​

Current agents include support for older GNOME Wayland sessions and GNOME Shell 51. They handle older Mutter screencast APIs instead of requiring every session to use the newer API path. On glibc systems, the agent tries the system PipeWire client library and falls back to its bundled library if a usable system library is unavailable. These compatibility paths do not guarantee capture on every GNOME release or login screen.

KDE Plasma

On KDE Plasma, the agent registers the access it needs with KWin automatically. No action required.

KDE's compositor capture uses PipeWire. If DMA-BUF capture produces no initial frame, the agent can renegotiate using shared-memory transfer. This addresses a capture problem seen on older KWin versions with software rendering; it is not a universal KDE version or graphics-driver guarantee.

If Remote Control Isn't Available After Install

Setup runs automatically and remote control should work right after the agent installs. If it doesn't, reboot the device.

💡 TIP: A reboot clears up nearly all first-time setup issues across every desktop environment, including GNOME extension activation and KDE access registration. If a freshly installed or upgraded device isn't accepting remote sessions, reboot it before digging further.


Linux Session Behaviors

A few things work slightly differently in a Linux session.
​

Multi-monitor is supported. Use the Display dropdown in the top toolbar to switch between monitors, the same as on other platforms.
​

Clipboard sharing works across desktop environments, including Wayland compositors beyond GNOME and KDE. Send Clipboard and Get Clipboard work as described in Remote Control. Text consoles do not provide a desktop clipboard.
​

Keyboard input in graphical sessions handles non-US layouts and Unicode characters, so typing in the session should match what you'd type locally. Text-console input uses the console keymap when available, with a system keyboard-layout fallback; arbitrary Unicode input is not available through that kernel-input path.


FAQ

  • Which Linux distros does remote control support? Remote control availability depends on the agent, session, display, and capture method rather than the distribution name. GNOME, KDE Plasma, COSMIC, wlroots compositors, and Xorg desktops have graphical-session paths. Text-only consoles can also work when the device exposes a display Level can capture. See the requirements above and Supported Platforms for agent OS requirements.

  • I can't start a remote session on my Linux server. What's wrong? A missing graphical desktop is no longer enough to explain the failure. Use an up-to-date agent and check whether the machine exposes an active KMS display or a supported text-console framebuffer. A serial-only server or VM without a capturable display still has no screen for Level to show. Use the Terminal in background management when no display can be captured.

  • Can I connect before anyone logs in? Yes, when a supported graphical login screen or capturable text-only console is available. A logged-in user is not required. Greeter compatibility depends on its session and capture path, so successful capture of a user's desktop does not guarantee capture of every login screen.

  • Remote control connects to my Wayland machine but the screen is blank. Why? On GNOME Wayland, update the Level agent first and retry before falling back to Xorg. Current agents include GNOME compatibility fixes, a shared-memory fallback for PipeWire capture, and direct KMS fallback for eligible sessions. These still require a working capture path and an available display. If capture remains unavailable, use background management while you check the compositor, display, and graphics-driver configuration.

  • I just installed the agent and remote control isn't available yet. Setup is automatic and should be ready immediately, but if a device isn't accepting sessions right after install or upgrade, reboot it. That resolves most first-time setup issues, including GNOME extension activation and KDE access registration.

  • Does the GNOME extension require any setup from the end user? No. The agent installs and enables it automatically for the logged-in user, and picks the right build for the installed GNOME Shell version.

  • Is the connection encrypted the same way as Windows and macOS? Yes. Linux sessions use the same end-to-end encrypted P2P connection, with relay fallback when a direct connection isn't possible. See the main Remote Control article for details.

Did this answer your question?