Sessions & Memory · recorded 2026-08-29 · applies to 1 tool(s) ✓ Verified

Problem: Architecture mismatch (ARM devices like Orange Pi) —— Trove problem library

Verified 2026-08-29ARM devices (Orange Pi etc.) reject x86 packages — check `dpkg --print-architecture` first, then install the matching deb.

Quick fix

# One-liner: check the architecture first, then install (arm64 example)
dpkg --print-architecture && sudo apt install ./cc-switch_arm64.deb

What you will run into

On ARM devices (Orange Pi etc.), installing the x86_64 package reports an architecture error, or you download the arm package and the GUI won't start.

The official release actually covers amd64/arm64 and other platforms (19 assets); the problem is usually not picking the asset by architecture, or the lightweight ARM system missing desktop libraries.

Why this happens

  • Wrong architecture installed: dpkg -i rejects mismatched architectures outright (wrong architecture);
  • Right arm64 package but GUI won't start: some lightweight ARM systems (no desktop / minimal distro) lack desktop libraries like GTK - the same dependency issue as symptom 1.

This error actually contains two independent checks, layer by layer: first, dpkg's architecture gate — a deb package carries an Architecture field in its metadata, and dpkg -i compares it with the system's dpkg --print-architecture, rejecting mismatches outright (wrong architecture).

This is a deliberate Debian-family design to keep wrong packages from breaking your system, so this error means you grabbed the wrong asset.

Second, dynamic-link dependencies — even with the right architecture, a GUI that won't start usually means missing desktop libraries like GTK/webkit2gtk.

The key difference: apt install ./xxx.deb resolves and pulls dependencies automatically, while bare dpkg -i does not. So "check the architecture first + install with apt" — both steps are required.

Step by step

1. Pick the right architecture asset — Required

uname -m

x86_64 -> amd64 asset; aarch64 -> arm64 asset. Filter the asset page by Architecture (x86_64 / arm64 / win / mac).

2. Install the arm64 package on an ARM desktop system — Required

sudo apt install ./cc-switch_arm64.deb

apt pulls the GUI dependencies automatically (libwebkit2gtk etc.).

3. No desktop environment — Required

Not recommended to install the GUI form; consider a CLI alternative (e.g. edit ~/.claude.json directly to switch).

How to confirm it works

cc-switch --version

Version prints and the GUI starts = success (AMD measured: package structure is ELF x86-64 31MB, install verification passed).

Other environments

EnvironmentNotes
Orange Pi etc. (ARM)Pick the arm64 asset + apt pulls dependencies
x86_64 desktopamd64 asset
Lightweight ARM without desktopGUI form not recommended; use the CLI alternative
Wrong architecture pickeddpkg reports wrong architecture outright; re-pick the asset

Symptom

On ARM devices (Orange Pi etc.), installing the x86_64 package reports an architecture error, or the GUI won't start after downloading the arm package (GTK issue).

Cause

The official 19 assets cover amd64/arm64 and other platforms; dpkg outright rejects a wrong-architecture package (wrong architecture); some lightweight ARM systems lack desktop libraries.

Solution

  1. Pick the right architecture asset (filter the asset page by Architecture: x86_64 / arm64 / win / mac).
  2. On ARM desktop systems install the arm64 package + matching GUI dependencies (same apt method as symptom 1).
  3. On devices without a desktop environment, don't install the GUI form (consider a CLI alternative).
Verification Evidence
  • Web case: CSDN (Orange Pi ARM architecture + GTK scenario).
  • Measured in this marketplace: amd64 package structure confirmed (/usr/bin/cc-switch, ELF x86-64, 31MB -).

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

cc-switch

Source & evidence

Recorded Verified ✓ VerifiedApplies to 1 tool(s)
Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Sessions & Memory domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk