Choose AppImage for a portable single-file app that runs on most distributions, or use a .deb package on Debian-based systems like Ubuntu, Linux Mint, and Pop!_OS.
Which package should I choose?
Portable · Most distributions
ITSDU-Linux-0.1.7.AppImageDownloadDownload the AppImage
Get ITSDU-Linux-0.1.7.AppImage from the downloads page.
Make it executable
Choose either approach.
GUI
Terminal
chmod +x ITSDU-Linux-0.1.7.AppImageRun it
Double-click the AppImage in your file manager, or from the terminal:
./ITSDU-Linux-0.1.7.AppImage.deb package
ITSDU-Linux-0.1.7.debDownloadDownload the .deb package
Get ITSDU-Linux-0.1.7.deb from the downloads page.
Install it with apt
From the directory where you downloaded the .deb:
sudo apt install ./ITSDU-Linux-0.1.7.debapt will resolve dependencies automatically.
Launch ITSDU
Open ITSDU from your application launcher, or run itsdu in a terminal.
If apt isn't available, you can install with dpkg and then resolve any missing dependencies:
sudo dpkg -i ITSDU-Linux-0.1.7.deb
sudo apt install -fThe file isn't marked as executable yet. From a terminal in the same folder:
chmod +x ITSDU-Linux-0.1.7.AppImageThen double-click again, or run it directly with ./ITSDU-Linux-0.1.7.AppImage.
Same fix — make the AppImage executable:
chmod +x ITSDU-Linux-0.1.7.AppImageUse apt instead of dpkg when possible — apt resolves dependencies for you:
sudo apt install ./ITSDU-Linux-0.1.7.debIf you already used dpkg and saw dependency problems, run sudo apt install -f to fix them.
Use .deb if you're on Debian, Ubuntu, Mint, Pop!_OS, or another Debian-based distribution. It integrates with apt and your system package manager.
Use AppImage otherwise — including Fedora, Arch, openSUSE, and any time you want a portable, no-install option.
Some newer distributions don't ship FUSE 2 by default. Most package managers can install it — for example on Ubuntu 22.04+:
sudo apt install libfuse2Stay safe
Only download ITSDU from itsdu.danielz.dev or the official GitHub releases linked from the downloads page. Don't install files shared through random links or re-uploaded elsewhere.
Open an issue on GitHub if something isn't covered here. Mention your distribution and the exact command output you saw — that's usually enough to spot the problem.