Running the AppImages¶
AppImage is a portable application format that runs on many Linux distributions without system installation.
AppImages are available for x86_64 and aarch64. They are not available for
Raspberry Pi.
Requirements
The AppImages need glibc 2.38 or later, the same as the .deb packages.
They also need the FUSE 2 runtime library. See
Install FUSE 2.
Step 1 - Install FUSE 2¶
AppImages mount themselves with FUSE 2. Recent distributions ship FUSE 3 and do not install FUSE 2, so install it first.
On Ubuntu 24.04 and newer, and Debian 13 and newer:
On older Debian and Ubuntu releases, the package is named libfuse2.
Run without installing FUSE
To run an AppImage on a system without FUSE 2, unpack it into a temporary directory at each start:
Without FUSE 2, and without this option, the AppImage stops with an error
about libfuse.so.2 or a failure to mount.
Step 2 - Make the AppImages executable¶
cd ~/Downloads
chmod +x ./RimuSDR-*.AppImage
chmod +x ./RimuDAX-*.AppImage
chmod +x ./RimuCAT-*.AppImage
Step 3 - Run the applications¶
Run the AppImages from your Downloads folder:
To start them by name from any directory, move them to ~/.local/bin/:
mkdir -p ~/.local/bin
mv RimuSDR-*.AppImage ~/.local/bin/
mv RimuDAX-*.AppImage ~/.local/bin/
mv RimuCAT-*.AppImage ~/.local/bin/
Log out and back in after you create ~/.local/bin
Debian and Ubuntu add ~/.local/bin to your PATH only if the directory
exists when you log in. If you created it with the command above, log out
and back in before the applications start by name.
To check that the directory is on your path, run echo $PATH.
After setup¶
- System integration
- None. AppImages do not appear in system menus by default.
- Launch
- Execute the
.AppImagefile. - Portability
- Move the file anywhere, or run it from a USB drive.
- Updates
- Manual. Download the new version when it is available.
Next, activate your license. See the Activation Guide.