Three steps
- Download the AppImage for your machine:
Intel or AMD (x86_64)
·
ARM64 (Raspberry Pi, Asahi)
- Make it executable. A browser always saves the file without that flag.
chmod +x NaviBeat-linux-*.AppImage
No terminal? Right-click the file, Properties, Permissions, tick Allow executing file as program. GNOME Files, Dolphin, Thunar and Nemo all have it.
- Run it:
./NaviBeat-linux-*.AppImage
The AppImage carries its own Java runtime, so you do not need to install Java. Runs on 64-bit Intel and AMD, and on ARM64 like a Raspberry Pi or Asahi Linux.
An AppImage does not really install, it is a single file you run. The natural home for it is a ~/Applications folder. For a menu entry and icon, use AppImageLauncher or AppManager.
Or install it with apt, dnf or pacman
NaviBeat has its own signed repository, so it arrives with a menu entry and an icon, and apt upgrade, dnf upgrade or pacman -Syu carries new versions along with everything else on the machine.
Copy each block whole, not one line at a time. The lines belong together, and in the Arch block everything between <<'EOF' and the closing EOF is one single command that writes the file. Paste only its first line and the shell waits for the rest instead of running anything.
Debian, Ubuntu, Raspberry Pi OS, Mint
sudo install -d /etc/apt/keyrings
curl -fsSL https://dl.navibeat.app/navibeat-repo.gpg \
| sudo tee /etc/apt/keyrings/navibeat.gpg >/dev/null
echo "deb [signed-by=/etc/apt/keyrings/navibeat.gpg] \
https://dl.navibeat.app/deb stable main" \
| sudo tee /etc/apt/sources.list.d/navibeat.list
sudo apt update && sudo apt install navibeat
Fedora 38 and newer
sudo dnf install https://dl.navibeat.app/navibeat-release.rpm
sudo dnf install navibeat
Arch Linux, and Arch Linux ARM
curl -fsSL https://dl.navibeat.app/navibeat-repo.asc -o /tmp/navibeat-repo.asc
sudo pacman-key --add /tmp/navibeat-repo.asc
sudo pacman-key --lsign-key 0940E93F0EA97642
sudo tee -a /etc/pacman.conf >/dev/null <<'EOF'
[navibeat]
SigLevel = Required
Server = https://dl.navibeat.app/arch/$arch
EOF
sudo pacman -Syu navibeat
The Debian and Fedora packages carry Java and VLC inside, the same as the full AppImage, so they depend on nothing but a C library and work on a Fedora that has never added RPM Fusion. The Arch package carries its own Java and uses the libvlc already in Arch's own repositories, which is how a package on Arch is expected to behave. x86_64 and ARM64 for all three.
Every package is signed. The key's fingerprint, so you can check the one you are asked to trust:
4ABC 7093 F4A6 6FFD EF71 6DAD 0940 E93F 0EA9 7642