01

Package format follows the distribution

The Linux section of the release page offers three formats. The .deb targets Debian, Ubuntu and Mint. The .rpm targets Fedora and openSUSE. AppImage does not care about the distribution at all.

The rule is short. If your system uses apt, take the .deb. If it uses dnf or zypper, take the .rpm. On Arch, NixOS or anything you cannot place confidently, use the AppImage. Architecture matters too: x86_64 for ordinary PCs, aarch64 for ARM boards such as a Raspberry Pi.

A same named package in your distribution repository is not necessarily the same software
Official builds appear only at github.com/clash-verge-rev/clash-verge-rev/releases, and third party packagings often lag several versions behind.

SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes
02

How each format installs and where each one bites

  1. 1

    deb: let apt collect the dependencies

    sudo dpkg -i plus the filename works but stops with an error when a dependency is missing. Follow it with sudo apt -f install and everything fills in. One command does the same job: sudo apt install ./package.deb. Keep the leading dot and slash, or apt searches the repository for that name.

  2. 2

    rpm: use the package manager, not the rpm command

    On Fedora run sudo dnf install ./package.rpm, on openSUSE sudo zypper install ./package.rpm. Plain rpm -i installs the file too, but it resolves nothing and every missing library becomes a manual hunt.

  3. 3

    AppImage: set the executable bit first

    A fresh download has no executable bit, so run chmod +x on it before launching. Several newer distributions ship only FUSE 3 and the AppImage then complains about a missing library. Install the libfuse2 compatibility package from your repository.

03

Tray and system proxy behave differently here

The desktop system proxy switch only reaches programs that read the GNOME or KDE proxy settings. Browsers honor it. Plenty of command line tools and Electron apps ignore it entirely, which produces the classic complaint that the proxy is on but curl still goes direct. TUN is the calmer answer on Linux, because it works at the network layer.

  • The tray icon is visible, remembering that GNOME ships without a tray and needs an AppIndicator style extension plus a re-login, while KDE and XFCE show it out of the box
  • The Logs page produces output and the port is free, meaning 7897 on current builds or 7890 in an older config
  • The first TUN attempt asks for a sudo password to grant network capabilities to the core binary or install the service
04

Common questions

There is no tray icon at all on GNOME. What now?

Confirm the process is running, then install a GNOME extension that provides AppIndicator support and log out and back in. Some distributions pin extensions tightly to the gnome-shell version, and an incompatible extension leaves you with no icon either way, so pick a maintained one.

Which is easier to keep updated, AppImage or deb?

A deb is recorded in the package database and uninstalls cleanly, but updating means downloading a new package by hand, since the release page provides no apt source. An AppImage is one file, so updating is replacing it and you can keep the old file to roll back. Both keep configuration in your home directory, and the exact path is whatever the open config directory action in the app opens.