Why Flatpak Apps Stop Opening on Linux Mint
Flatpak has become the preferred way to install modern applications on Linux Mint, offering sandboxed environments and easy access to the latest software versions through Flathub. However, many users encounter a frustrating situation where Flatpak apps simply refuse to launch — no error message, no window, nothing happens. In 2026, this is still one of the most reported issues on the Linux Mint Forums.
The root causes range from outdated runtimes and graphics driver mismatches to broken Flatpak installations and missing Flathub configuration. This guide walks through every known fix, from quick one-liners to a full Flatpak reinstall.
Step 1: Run the App from Terminal to See the Real Error
Before doing anything else, open a terminal and run the failing app manually. Clicking the icon in the menu hides all output, but the terminal shows exactly what went wrong.
Find the app's Flatpak application ID first:
flatpak list --appThen run it:
flatpak run com.example.AppNameCommon error patterns and what they mean:
- error: app/com.example.App/... not installed — the app is partially installed or corrupted.
- bwrap: ... No such file or directory — a runtime or extension is missing.
- libGL error / MESA-LOADER — graphics runtime mismatch after a driver update.
- Gtk-WARNING: cannot open display — Wayland/X11 session issue.
Step 2: Update Flatpak and All Runtimes
An outdated Flatpak runtime is the most common cause of apps silently failing to launch. A single command updates both the Flatpak framework and all installed runtimes:
flatpak updateIf you want to update only a specific app:
flatpak update com.example.AppNameAfter updating, reboot or at minimum log out and back in, then try launching the app again. In many cases this alone resolves the issue.
If your Flatpak version itself is outdated (check with flatpak --version), update it via the system package manager:
sudo apt update && sudo apt install --only-upgrade flatpakStep 3: Repair the Flatpak Installation
If updating does not fix the problem, the local Flatpak cache or OCI bundle may be corrupted. The built-in repair command checks and fixes inconsistencies:
flatpak repairThis command scans every installed app and runtime, verifies checksums, and redownloads anything that is broken. It is safe to run at any time and does not delete user data stored inside app sandboxes.
For a user-only installation (apps installed without sudo), run:
flatpak repair --userAfter the repair completes, run flatpak update once more to ensure all runtimes are at the latest version before retesting the app.
Step 4: Fix Graphics Driver and Runtime Mismatch
After installing or updating NVIDIA, AMD, or Intel graphics drivers, Flatpak apps that use GPU acceleration (browsers, media players, games, Electron apps) often stop launching. This happens because the Flatpak graphics runtime no longer matches the host driver version.
Check which graphics extension packages are installed:
flatpak list | grep -i mesa
flatpak list | grep -i nvidiaUpdate the graphics extensions specifically:
flatpak update org.freedesktop.Platform.GL.default
flatpak update org.freedesktop.Platform.GL32.defaultFor NVIDIA users, the extension package name includes the driver version. If Flatpak cannot find a matching extension, the quickest fix is to reinstall the affected app:
flatpak uninstall com.example.AppName
flatpak install flathub com.example.AppNameA fresh install triggers resolution of all current runtime and extension dependencies, which resolves version mismatches automatically.
Step 5: Verify the Flathub Remote is Correctly Configured
If Flatpak apps were installed from Flathub but the remote repository becomes misconfigured or points to a stale endpoint, apps can fail silently. Check the list of configured remotes:
flatpak remotesYou should see flathub in the list pointing to https://dl.flathub.org/repo/. If it is missing or shows an error, re-add it:
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepoIf the remote exists but is disabled, re-enable it:
flatpak remote-modify --enable flathubThen run flatpak update again to pull fresh metadata from Flathub.
Step 6: Fix Flatpak Apps Not Showing or Launching from the Menu
Sometimes Flatpak apps install correctly but their menu launchers fail to open them. This is common on Linux Mint Cinnamon and XFCE after a desktop update.
Rebuild the desktop database
update-desktop-database ~/.local/share/applications/
flatpak run --command=update-desktop-database com.example.AppName 2>/dev/null || trueRefresh the application menu
On Cinnamon, right-click the taskbar and choose Applets, then select the menu applet and click Reload. Alternatively, restart the Cinnamon shell:
cinnamon --replace &On XFCE, update the whiskermenu plugin if it is below version 2.8.3, as older versions fail to launch Flatpak apps installed via terminal:
sudo apt install xfce4-whiskermenu-pluginCheck for permission issues in the launcher file
Inspect the desktop file that Flatpak creates:
cat ~/.local/share/applications/com.example.AppName.desktopEnsure the Exec= line starts with flatpak run and the file has execute permission:
chmod +x ~/.local/share/applications/com.example.AppName.desktopStep 7: Complete Flatpak Reinstall (Last Resort)
If none of the above steps resolve the issue, a clean reinstall of the entire Flatpak stack is the most reliable fix. This removes all Flatpak apps and runtimes, then starts fresh.
Warning: This removes all Flatpak apps. App data in ~/.var/app/ is preserved by default unless you pass --delete-data.
# Remove all apps
flatpak uninstall --all
# Remove unused runtimes
flatpak uninstall --unused
# Reinstall Flatpak itself
sudo apt remove --purge flatpak
sudo apt install flatpak
# Re-add Flathub
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
# Reinstall apps
flatpak install flathub com.example.AppNameAfter a clean reinstall, all apps are pulled fresh with correct, matched runtimes.
When to Get Expert Help
Some Flatpak failures are caused by deeper system issues — SELinux policies, AppArmor profiles blocking sandbox namespaces, or kernel namespace restrictions introduced by a security patch. These require examining journalctl -f output while launching the app, and sometimes editing kernel boot parameters.
If you have worked through every step in this guide and Flatpak apps still refuse to open, Get expert help from CloudHouse Technologies. Our Linux-certified technicians can remotely diagnose sandbox failures, driver conflicts, and configuration issues that fall outside standard troubleshooting guides.
Frequently Asked Questions
Why did my Flatpak apps stop working after a system update?
System updates often include new graphics drivers or kernel versions that break the compatibility between the host environment and Flatpak's runtime extensions. Run flatpak update immediately after any major system update to sync the runtimes with the new host libraries.
How do I find the app ID for a Flatpak app?
Run flatpak list --app in a terminal. Each row shows the app name, application ID (e.g., org.gimp.GIMP), version, branch, and installation origin. Use the Application ID with flatpak run and flatpak uninstall commands.
Can I run a Flatpak app as root on Linux Mint?
Running Flatpak apps as root is not recommended and is blocked by default for security reasons. If a specific app requires elevated permissions, use flatpak override --user --filesystem=host com.example.App to grant broader filesystem access without running as root.
Why does my Flatpak app crash only on Wayland but work on X11?
Some Flatpak apps have incomplete Wayland support. Force the app to run on XWayland by setting the environment variable: flatpak run --env=GDK_BACKEND=x11 com.example.AppName. For a permanent fix, use flatpak override --env=GDK_BACKEND=x11 com.example.AppName.
Does reinstalling a Flatpak app delete my saved data?
No. Flatpak stores user data in ~/.var/app/com.example.AppName/, which is separate from the app installation. Running flatpak uninstall without --delete-data preserves all your settings, save files, and configuration. The data is automatically picked up when you reinstall the app.