RustDesk is an open-source remote desktop client that works on major Linux distributions. Install the package that matches your distribution, open RustDesk on both computers, enter the remote computer's ID, and authenticate with its one-time or permanent password. By default, the client can use RustDesk's public infrastructure; running your own server is optional.
Download RustDesk only from the official RustDesk releases page or follow the official Linux installation guide. Avoid old version-specific download links because package names and supported architectures change between releases.
Choose the build for your CPU architecture, then install it with the package manager for your distribution. RustDesk's current Linux documentation recommends the following package formats:
| Linux distribution | Package | Install command |
|---|---|---|
| Ubuntu / Debian-based | .deb | sudo apt install -fy ./rustdesk-<version>.deb |
| Fedora / CentOS-based | .rpm | sudo yum localinstall ./rustdesk-<version>.rpm |
| Arch Linux / Manjaro | .pkg.tar.zst | sudo pacman -U ./rustdesk-<version>.pkg.tar.zst |
| openSUSE | SUSE-specific .rpm | sudo zypper install --allow-unsigned-rpm ./rustdesk-<version>-suse.rpm |
RustDesk also publishes AppImage and Flatpak builds. For Flatpak, the official guide uses flatpak --user install ./rustdesk-<version>.flatpak, followed by flatpak run com.rustdesk.RustDesk.
Launch RustDesk on the Linux computer and on the machine you want to reach. When the client is ready, the home screen shows the local ID and a one-time password. The ID identifies the device; the password authenticates the connection.
On the controlling computer, type the other computer's ID into the Control Remote Desktop field and select Connect. Do not share your own password with someone unless you intend to let that person access your computer.
Enter the password shown on the remote computer. Depending on the remote device's security settings, the person at that computer may also be able to approve the connection manually. RustDesk's Security settings let the owner choose how incoming sessions are approved and which remote-control permissions are available.
After authentication, the remote desktop opens in a RustDesk session window. Keyboard and mouse control, clipboard synchronization, and other capabilities depend on permissions enabled on the computer being controlled. If input or clipboard access is unavailable, check Settings > Security on the remote device rather than repeatedly reconnecting.
Use the session toolbar's Disconnect button to close the remote connection. This ends the active session without shutting down the remote computer.
If you need to connect when nobody is available to read the one-time password or approve the session, open Settings > Security on the computer being controlled and set a strong, unique permanent password. RustDesk's current unattended-access guidance recommends using a dedicated password rather than reusing the operating-system login password.
For access before a user signs in or after a logout, display-server behavior matters on Linux. RustDesk documents Wayland support as experimental and says remote access to a Wayland login screen is not supported. If you must reach the login screen after reboot or logout, RustDesk's Linux documentation recommends using X11 for the login screen.
A basic connection does not require you to self-host anything. If you already run RustDesk Server OSS or Server Pro, open the menu next to your ID, go to Network, unlock the network settings, and enter the server details supplied by your deployment. According to the official client configuration guide, most self-hosted clients need the ID Server and its public Key; a Relay Server can often be inferred, while the API Server is used with Server Pro features.
avc: denied, follow RustDesk's SELinux guidance in the official Linux documentation rather than disabling SELinux globally.For routine use, the simplest workflow is: install the correct Linux package, exchange the remote device ID securely, authenticate, work in the session, and disconnect when finished.
Capture Linux desktop audio in Audacity by routing its recording stream to your output device’s monitor source. Follow PulseAudio and PipeWire steps, export tips, and fixes for silent tracks.
Install Dropbox on Linux from the official package, sign in, sync a local folder, manage selective sync, and check status from the command line.
Install Inkscape from your Linux distribution’s repositories, the Ubuntu stable PPA, Snap, or Flathub, with current commands and notes for choosing a package source.
Use FSlint to scan selected Linux folders, review duplicate groups, and safely delete redundant files or learn when hard-link merging is appropriate.
Install SABnzbd on Ubuntu or Debian, or run it in Docker on another Linux host. Then open the web interface and configure your provider and download folders.
Install the Paper GTK theme from supported Linux repositories, enable it for GTK apps in GNOME Tweaks, and see what the legacy theme can and cannot change.
The old OpenMediaVault Plex plugin is archived. Set up Plex on OMV 8 with OMV-Extras, the Compose plugin, persistent storage, and Plex’s official container.
Clean and speed up Ubuntu with safe APT cleanup, storage checks, and startup controls that help free space and troubleshoot a sluggish desktop.
Install Hiri on Linux with its Snap package or official tarball, add a desktop launcher, and check supported accounts plus a warning about Hiri’s old Snap release.
Use Fastfetch and built-in Linux commands to check your distro, kernel, CPU, memory, graphics, storage, and connected devices, then save a clear report.
