The Linux tray is built on Ubuntu and reused in Debian and Arch packages. Its default tray-icon feature pulls in libxdo through muda, tying the binary to the builder's libxdo SONAME. Arch now supplies libxdo.so.4 while existing release binaries can require libxdo.so.3. Disable tray-icon default features: libxdo only supports predefined clipboard menu actions, while our tray uses Open, Quit and a separator. Keep GTK support. Regenerate Cargo.lock without upgrading other packages, and remove libxdo build/runtime dependencies from both release workflows, Debian/Arch packaging and Nix. Update the Arch installation notes. Clarify that static Linux CLI binaries are release artifacts built for musl; ordinary host-target Cargo builds on glibc Linux are dynamic. Document the existing musl build command and its output path. Both release workflows still package the musl tsng independently of the GNU tray. No protocol, persistent state, crate version or release tag changes. Validation on macOS: - cargo fmt --all -- --check - cargo clippy --locked --workspace --all-targets -- -D warnings - cargo test --locked --workspace --all-targets: 532 passed, 2 ignored - bash -n dist/arch/build-pkg.sh dist/deb/build-deb.sh - Linux-target Cargo dependency graph retains GTK and contains no libxdo; resolved metadata contains neither libxdo nor libxdo-sys - git diff --check Initial offline resolution lacked smoltcp and sandboxed registry access failed; resolution succeeded with approved network access. The first sandboxed test run failed when child agents exited before readiness; the full run outside the sandbox passed. Linux release binaries, native GUI startup, packages and Nix builds were not run locally; CI/release execution is left to the user.
1.7 KiB
Running tsunagi on Arch Linux
Install the package built for your architecture:
sudo pacman -U tsunagi-*-x86_64.pkg.tar.zst
It drops a static, dependency-free binary at /usr/bin/tsng, a systemd
service, and a polkit rule, and creates a dedicated system user tsunagi the
service runs as.
Start it:
sudo systemctl enable --now tsunagi
Control it with sudo (the agent's control socket is private to the service
user; sudo reaches it with no extra flags, because the CLI finds the running
service's socket at /run/tsunagi/agent.sock):
sudo tsng status
sudo tsng join -n <network-name> -s <tsn1…secret>
How it runs
The service runs as the unprivileged tsunagi user with just two capabilities
(CAP_NET_ADMIN, CAP_NET_BIND_SERVICE) granted by systemd — no root. systemd
creates and owns its directories:
| what | path |
|---|---|
| state | /var/lib/tsunagi |
| cache | /var/cache/tsunagi |
| control socket | /run/tsunagi/agent.sock |
Installing the package enables and starts the service, and adds the user who ran
pacman to the tsunagi group (log out and in again for it to apply). The
control socket is open to that group, so members can run tsng status, the
CLI and the tray GUI without sudo; anyone else adds themselves with sudo usermod -aG tsunagi "$USER". The group also lets its members configure
systemd-resolved for the overlay zones through the polkit rule.
The GUI package depends on gtk3, libayatana-appindicator (the tray icon),
and the usual windowing libraries.
Removal
sudo pacman -R tsunagi
stops and disables the service. The tsunagi user and /var/lib/tsunagi are
left in place; remove them by hand if you want them gone.