On Linux Mint, upgrading Flatpak usually means updating the apps and runtimes you already use, not replacing the flatpak package itself. That is why how to upgrade Flatpak on Linux Mint can mean two jobs: run flatpak update, or move the package to a newer release through the stable PPA.
The package-level path only matters when the Mint archives lag behind a Flatpak fix or feature you need. You can confirm the newer candidate first, upgrade only the Flatpak package set, and roll back cleanly if the PPA causes problems.
Upgrade Flatpak on Linux Mint
Linux Mint 22.x ships Flatpak 1.14.x from its Ubuntu 24.04 base, while Linux Mint 21.x ships Flatpak 1.12.x from its Ubuntu 22.04 base. The Flatpak stable PPA currently publishes Flatpak 1.16.x for both supported Mint releases, which is newer than the Mint archives even though it does not always match the newest upstream tag on release day.
| Linux Mint release | Ubuntu base | Archive Flatpak | Flatpak stable PPA |
|---|---|---|---|
| Linux Mint 22.x | Ubuntu 24.04 LTS | Flatpak 1.14.x | Flatpak 1.16.x |
| Linux Mint 21.x | Ubuntu 22.04 LTS | Flatpak 1.12.x | Flatpak 1.16.x |
Default Linux Mint desktop installs already include Flatpak and a system
flathubremote. If you only want newer Flatpak applications and runtimes, skip the PPA and use the app and runtime update commands instead.
Refresh Linux Mint Package Metadata Before the Flatpak Upgrade
Open a terminal from the applications menu or by using the keyboard shortcut configured on your system, then refresh the package lists before you add the PPA:
sudo apt update && sudo apt upgradeThis guide uses
sudofor APT commands. If your account does not have sudo access yet, follow the guide on how to create and add users to sudoers on Linux Mint.
Add the Flatpak Stable PPA
The stable PPA is the only PPA this guide recommends. The development PPA currently publishes an older Flatpak build than the stable channel, so it does not improve the upgrade path on supported Mint releases.
sudo add-apt-repository -y ppa:flatpak/stableMint 22.x creates flatpak-stable-noble.list, while Mint 21.x creates flatpak-stable-jammy.list. That .list file is normal for PPA-based configuration on Linux Mint.
Refresh APT after the PPA is added, then confirm that the new candidate comes from ppa.launchpadcontent.net:
sudo apt updateHit:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:5 http://packages.linuxmint.com zara Release Get:8 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu noble InRelease [17.8 kB] Get:9 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu noble/main amd64 Packages [2,624 B] Reading package lists...
apt-cache policy flatpakflatpak:
Installed: 1.14.6-1ubuntu0.1
Candidate: 1.16.1-1~flatpak1~24.04.1
Version table:
1.16.1-1~flatpak1~24.04.1 500
500 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu noble/main amd64 Packages
On Mint 21.x, the same check shows the jammy branch and a 1.16.1-1~flatpak1~22.04.1 candidate.
Upgrade the Flatpak Package
Use a single-package upgrade so APT only touches the Flatpak package set. APT also upgrades bubblewrap, libflatpak0, and gir1.2-flatpak-1.0 because those packages move with Flatpak in the PPA.
sudo apt install --only-upgrade flatpakThe following additional packages will be installed: bubblewrap gir1.2-flatpak-1.0 libflatpak0 The following packages will be upgraded: bubblewrap flatpak gir1.2-flatpak-1.0 libflatpak0 4 to upgrade, 0 to newly install, 0 to remove and 2 not to upgrade. Need to get 1,863 kB of archives. Setting up flatpak (1.16.1-1~flatpak1~24.04.1) ...
Verify the Flatpak Version
flatpak --versionFlatpak 1.16.1
Mint 21.x also upgraded to Flatpak 1.16.1 from the stable PPA during verification.
Update Flatpak Apps and Runtimes on Linux Mint
This is the command path most readers actually need. Upgrading the flatpak package through APT does not update the installed apps and runtimes inside your Flatpak remotes.
Check or Add the Flathub Remote on Linux Mint
Linux Mint should already have Flathub enabled system-wide. Confirm that before you update applications:
flatpak remotesflathub system
If flatpak remotes does not show flathub, you are probably working on a customized desktop install or a test VM instead of Mint’s default setup. Add the remote manually, then rerun the same check:
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepoThe --if-not-exists flag skips the add if Flathub is already present.
Update Flatpak Apps and Runtimes
Refresh every installed Flatpak application and runtime with one command:
flatpak updateLooking for updates... Nothing to do.
If you only want one application, append its app ID, such as flatpak update org.videolan.VLC.
Troubleshoot Flatpak Package Upgrades on Linux Mint
The most common problems after a Flatpak package upgrade are an unchanged APT candidate and app launch errors caused by stale runtime metadata.
Fix a Flatpak Candidate That Does Not Change
If sudo apt install --only-upgrade flatpak reports that nothing can be upgraded, refresh APT again and inspect the candidate package directly:
sudo apt update && apt-cache policy flatpakflatpak:
Installed: 1.14.6-1ubuntu0.1
Candidate: 1.16.1-1~flatpak1~24.04.1
Version table:
1.16.1-1~flatpak1~24.04.1 500
500 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu noble/main amd64 Packages
If the candidate still points to the Mint archive version, add the stable PPA again and make sure the new flatpak-stable-*.list file exists in /etc/apt/sources.list.d/.
Fix Missing Runtime Errors After a Flatpak Upgrade
A newer Flatpak package does not refresh app runtimes by itself. When an app fails with a runtime error, update the installed Flatpak content first:
error: app/com.spotify.Client/x86_64/stable requires runtime org.freedesktop.Platform/x86_64/24.08 which was not found
flatpak updateLooking for updates... Nothing to do.
If flatpak update finishes cleanly and the app still fails, confirm that flathub is present in flatpak remotes and then reinstall the affected application from the same remote.
Downgrade Flatpak on Linux Mint
If the stable PPA introduces a regression in your workflow, remove the PPA and downgrade the Flatpak package set back to the Mint archive. Keep this rollback scoped to the Flatpak packages so you do not disturb unrelated desktop components.
Avoid
ppa-purgefor this rollback on Linux Mint. Downgrading Flatpak from the PPA can remove desktop packages along withflatpak, so the safer path is to target the Mint archive packages explicitly with--allow-downgrades.
Remove the Flatpak Stable PPA
sudo add-apt-repository --remove -y ppa:flatpak/stablesudo apt updateDowngrade Flatpak on Linux Mint 22.x
Mint 22.x is based on Ubuntu 24.04, so target the noble-updates pocket during the rollback:
sudo apt install --allow-downgrades -y flatpak/noble-updates libflatpak0/noble-updates gir1.2-flatpak-1.0/noble-updates bubblewrap/noble-updatesDowngrade Flatpak on Linux Mint 21.x
Mint 21.x is based on Ubuntu 22.04, so target the jammy-updates pocket instead:
sudo apt install --allow-downgrades -y flatpak/jammy-updates libflatpak0/jammy-updates gir1.2-flatpak-1.0/jammy-updates bubblewrap/jammy-updatesThese noble-updates and jammy-updates targets are the Ubuntu archive pockets underneath Linux Mint. They tell APT exactly where the downgraded Flatpak package set should come from.
Verify the Flatpak Rollback
flatpak --versionFlatpak 1.14.6
On Mint 21.x, the same rollback returns Flatpak 1.12.7 from the archive.
Frequently Asked Questions
Yes. Default desktop installs of Linux Mint 22.x and 21.x include flatpak with a system flathub remote. Confirm with flatpak --version and flatpak remotes if you are working on a customized install or VM.
Usually no. Linux Mint desktop installs already configure flathub system-wide. Add it manually only when flatpak remotes does not list flathub.
Use flatpak update. That refreshes installed applications and runtimes from your configured remotes. It is separate from upgrading the flatpak package itself through APT.
Upgrading Flatpak through APT changes the underlying flatpak, libflatpak0, gir1.2-flatpak-1.0, and bubblewrap packages. Updating Flatpak apps uses flatpak update to refresh applications and runtimes from flathub.
Not for normal desktop use. The current published build in ppa:flatpak/development is older than the stable PPA, so it does not provide a better upgrade path on supported Mint releases. Use the stable PPA unless you have a very specific packaging reason to test the development branch.
Conclusion
Flatpak is up to date on your Linux Mint system, either from the default archive or the stable PPA, and flatpak update keeps apps and runtimes in sync after that package decision is made. From there, you can install Chromium Browser on Linux Mint or install Steam on Linux Mint as two straightforward desktop app examples.
I am so sick of LINUX GOOFS who want everybody to use the terminal to upgrade and make Linux COMPLEX for regular users: “Here are the 50 f’n comands you need to know!”
I use UPDATE MANAGER. When updating, a box appears for updating Flatpacks:
Additional Changes Are Required
REMOVE
UPGRADE
What do they mean and which should you use? The Default appears to be REMOVE. Correct??? What does it do to your Flatpack? What does UPGRADE do?
This is all the information regular users of Linux Mint require for upgrading. Can you HELP?
You make a fair point, Doug. That Update Manager dialog is confusing. Choose UPGRADE. It updates your Flatpak apps to newer versions while keeping your data and settings intact.
REMOVE uninstalls old runtime versions that apps no longer need. This happens automatically after upgrades. Linux Mint changed the default to UPGRADE in recent releases to match what most users expect.
The terminal commands in the guide offer more control (rolling back, switching channels, fixing stuck updates), but you are right that Update Manager handles routine upgrades for most users. Both approaches work.