Clash Party Linux: DEB, RPM, and Arch Packages

Choose DEB, RPM, or PACMAN from the distribution family

Clash Party is the current project name continuing the application previously called Mihomo Party. At the time this article was checked, the official GitHub Releases page listed Linux DEB, RPM, and PACMAN packages for both 64-bit x86 and ARM64. These are packaging choices, not editions with different proxy features. The format determines which native package manager records files, resolves dependencies, upgrades the application, and removes it later.

Distribution family	Preferred asset	Suffix
Debian, Ubuntu, Linux Mint	DEB	`.deb`
Fedora and compatible RHEL-family systems	RPM	`.rpm`
Arch Linux and Manjaro	PACMAN	`.pkg.tar.zst`

A distribution derived from one of these families can still carry different library versions, desktop sessions, and security policy. Confirm the package manager actually used by the installed system. Extracting a DEB and copying files onto Arch may appear expedient, but it bypasses dependency and uninstall records and creates a harder upgrade problem.

Map x86_64 to amd64 and aarch64 to arm64

In release asset names, amd64 generally denotes the same 64-bit x86 architecture that Linux reports as x86_64. Likewise, arm64 generally corresponds to aarch64. Both are “64-bit,” but their binaries are not interchangeable. A laptop brand or the phrase “64-bit OS” is therefore insufficient evidence.

Shelluname -m

# An additional check on Debian or Ubuntu
dpkg --print-architecture

# An additional check on an RPM system
rpm --eval '%{_arch}'

For x86_64, choose the matching amd64, x64, or x86_64 asset named by that packaging format. For aarch64, choose arm64 or aarch64. Do not assume that 32-bit x86, ARMv7, LoongArch, or another result will run either package. If the official release does not offer the host architecture, stop rather than forcing the package manager past its safety check.

Check the actual host: a shell inside a container or on a remote machine may not describe the desktop on which the GUI will be installed.

Match the release, file name, and checksum

Open the official Releases page, read the notes for the intended version, and expand its Assets list. On 6 September 2026, the first release shown there was v2.0.2. A later reader must use the stable release shown at that time; this article does not turn v2.0.2 into a permanently “latest” version.

An official asset name identifies the platform, release, CPU, and format. Download the corresponding .sha256 sidecar when the release supplies one, and ensure it belongs to the exact same asset—not another version or architecture.

Shellsha256sum clash-party-linux-VERSION-ARCH.PACKAGE

# Compare the output with the matching sidecar in the same Release.

A matching digest detects corruption or substitution after publication, but does not transform an unofficial mirror into a trusted source. The page and repository owner should remain github.com/mihomo-party-org/clash-party. Search ads, repackaged cloud-drive files, and opaque “one-line installers” are outside that provenance chain.

Install the local asset with the native package manager

Run the command for the installed distribution from the download directory, replacing the placeholder with the exact file name. The ./ prefix matters because it identifies a local package. Install one asset at a time rather than mixing files from different releases.

Shell# Debian / Ubuntu
sudo apt install ./clash-party-linux-VERSION-amd64.deb

# Fedora and other systems using DNF
sudo dnf install ./clash-party-linux-VERSION-x86_64.rpm

# Arch Linux / Manjaro
sudo pacman -U ./clash-party-linux-VERSION-x64.pkg.tar.zst

The package manager checks architecture, registers installed paths, and resolves dependencies that are available in configured repositories. An architecture error calls for the correct asset. An unsatisfied dependency calls for checking the distribution release and repository state, not downloading random shared libraries. Other RPM distributions may use a different frontend and should follow their own official documentation.

Do not pipe an unknown installer into a shell: downloading, checking provenance and digest, and then installing a local package leaves a much clearer audit trail.

Separate first-launch problems from TUN permission

Start the application from the desktop menu. If no window appears, launch the installed command from a terminal once and preserve the first useful error. Check the graphical session, missing libraries, configuration-directory permissions, and an old running process before changing formats. The application payload in DEB and RPM is not a remedy for a Wayland, X11, or home-directory problem.

Confirm that the package manager completed installation.
Look for a Clash Party desktop entry.
Start once from a terminal and capture the specific error.
Confirm that the current user can write the application configuration directory.
After importing a profile, verify the system proxy before requesting TUN privileges.

TUN creates an additional virtual adapter and routes and therefore has a separate privilege boundary. A TUN failure does not prove that the desktop package failed to install. Establish the GUI, core, and system proxy first. A headless server is also not the normal environment for this Electron desktop application, so the absence of a display should not be diagnosed as the wrong download format.

Use the same package system for upgrades and removal

Before an upgrade, export important configuration and read the release notes. Download the new version in the same format and architecture, then install it with the same package manager. Do not keep a manually extracted copy beside the managed installation; a desktop shortcut may launch the unintended binary. Before a downgrade, consider whether newer configuration data remains compatible and retain a backup.

For removal, query the registered package name first and then decide whether user configuration should remain. The project rename and distribution packaging can make the registered name differ from the downloaded file name, so a blind delete command is inappropriate. Asset naming and packaging can be checked against the official build workflow. Local-package behavior is documented by the Debian apt manual and Arch pacman manual.

The durable decision has two inputs: the distribution selects the package format, and the CPU selects the architecture. The version, file, and checksum must come from one official release; the local package manager is the authority on whether installation completed.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.