How to Install a .deb File on Ubuntu, Debian & Mint (and Fix the Errors)

Quick answer: open a terminal in the folder containing the file and run:

sudo apt install ./your-package.deb

The ./ prefix matters — it tells apt you mean a local file, not a repository package. This one command installs the package and pulls in any dependencies it needs, which is exactly what double-clicking often fails to do. Everything below explains why the graphical route breaks so often, three alternative methods, and how to fix the errors you're most likely to hit.

Why Double-Clicking a .deb Often Does Nothing

On a fresh Ubuntu install, double-clicking a downloaded .deb opens App Center (or Ubuntu Software / GNOME Software on older releases). This route fails more often than it works, for reasons that are well documented across Ubuntu's own forums:

• On several Ubuntu releases the store app opens the file and then hangs on a spinner, or shows an Install button that silently does nothing.
• The store apps sometimes fail to resolve the package's dependencies, then give up without a readable error.
• On some systems .deb files aren't associated with an installer at all — double-clicking opens the Archive Manager, which shows you the package's internal folders instead of installing it. If you're looking at control.tar and data.tar, that's what happened; close it and use the terminal method.

None of this means the file you downloaded is broken. It's the GUI path that's unreliable — the terminal path below works on every Debian-family distribution.

Method 1: apt (Recommended)

cd ~/Downloads
sudo apt install ./your-package.deb

Type your account password when prompted (the cursor won't move while you type — that's normal), press Enter, and apt resolves dependencies, installs them, then installs your package. The app then appears in your application menu like any other program.

Common trip-up: running sudo apt install your-package.deb without ./ makes apt search the online repositories for a package literally named your-package.deb and fail with "Unable to locate package". Always include the ./ (or use the full path, e.g. sudo apt install ~/Downloads/your-package.deb).

Method 2: dpkg (the Classic Way)

sudo dpkg -i your-package.deb
sudo apt-get install -f

dpkg -i installs the package but does not resolve dependencies — if any are missing, it stops half-way and reports "dependency problems". The second command ("fix broken") downloads whatever was missing and completes the install. If you've ever ended up with a "half-installed" package blocking other updates, this pair also cleans that up.

Method 3: gdebi (Nice Lightweight GUI)

sudo apt install gdebi

Then right-click your .deb → Open With → GDebi Package Installer. GDebi shows you what the package will install, resolves dependencies properly, and is far more reliable than the store apps. Linux Mint ships GDebi by default, which is why double-clicking a .deb on Mint usually just works while the same file struggles on stock Ubuntu.

Fixing the Most Common Errors

"Dependency is not satisfiable: …" The package needs a library your system doesn't have and apt couldn't find. Run sudo apt update first (a stale package index is the usual cause), then retry Method 1. If the named dependency genuinely isn't in your release's repositories, your distribution version may be older than the app supports — check the app's minimum requirements.

"package architecture (amd64) does not match system (arm64)" (or vice versa) You downloaded the build for the wrong CPU type. Standard Intel/AMD PCs need amd64 (x64); Raspberry Pi and ARM laptops need arm64. Check which one you grabbed — most vendors publish x64 by default.

"Unable to locate package" You forgot the ./ prefix — see Method 1.

Terminal says "Permission denied" You ran the command without sudo. Installing software system-wide always requires it.

App Center / Ubuntu Software opens and hangs Skip it entirely — use Method 1. This is the single most-reported .deb frustration on modern Ubuntu, and the terminal bypasses it completely.

Example: Installing Lightning Assist from the .deb

Everything above applies to any .deb. Here's the full sequence for Lightning Assist (our text expander + voice-to-text app for Linux, Windows and macOS) as a concrete example — from download to a working app:

cd ~/Downloads
sudo apt install ./lightning-assist_*_amd64.deb

Then launch Lightning Assist from your application menu (or run lightning-assist in the terminal). On first launch, create your account or sign in — the 14-day free trial starts automatically, no credit card needed. The .deb works on Ubuntu 20.04–26.04, Debian 11+, Linux Mint and Pop!_OS.

If the .deb route still fights you, use the AppImage instead — it's the zero-install option and runs on every 64-bit distribution (including Fedora and openSUSE, which don't use .deb at all):

cd ~/Downloads
chmod +x Lightning*.AppImage
./Lightning*.AppImage

Both downloads are on the downloads page. For what to do after installing — permissions, first snippet, voice setup — see the complete installation guide, and if you're comparing options first, the best Linux text expanders in 2026 roundup covers the whole field.

FAQ

Do I need to uninstall the old version before installing a new .deb? No. sudo apt install ./package.deb upgrades an existing installation in place, keeping your settings.

How do I uninstall a package that came from a .deb? sudo apt remove package-name — the package name (e.g. lightning-assist), not the filename. sudo apt purge package-name also removes system-level config files.

Is the .deb or the AppImage better? .deb integrates with your system: menu entry, updates via your package manager, cleaner uninstall. AppImage needs no installation or root access and works across all distros. If the .deb gives you any trouble, the AppImage is the pragmatic fallback — same app either way.

Can I install a .deb on Fedora, openSUSE or Arch? Not directly — .deb is Debian-family only. Use the vendor's AppImage, Flatpak or native package instead. Converting with alien technically exists but breaks dependencies often enough that it isn't worth it.

Is downloading .deb files from websites safe? As safe as the site you download from — a .deb runs install scripts as root, so only install packages from vendors you trust, and prefer HTTPS downloads from the official site over mirrors.