Anyone who has installed a Flatpak application and found it stubbornly unable to open a folder or see a connected drive has met a quiet tension in modern Linux: each app lives in its own sealed room, and its makers decide which windows open onto the rest of the house. How-To Geek's latest guide gathers three tools that let ordinary users reopen some of those windows, retrieve the clutter left behind by departed software, and step back in time when an update goes wrong. The author's judgment, offered as opinion rather than measured testing, is that these three will serve most desktop users well
Three Linux Apps That Tackle Flatpak's Worst Permission and Storage Headaches
Uninstalling a Flatpak does not necessarily remove its configuration files
Mark
Why do Flatpak apps fail to open files in the first place?
Mimi
Because they run in sandboxes. Developers declare what the app can reach on the host, and those limits can be tighter than with a traditional RPM or DEB package.
Mark
So Flatseal is the fix for that?
Mimi
It's the graphical one. You choose an app and toggle filesystem, device, and socket access, then restart the app. There's a reset option too.
Luke
Worth noting this is one writer's opinion. He says Flatseal should be among the first things you install, but that's a recommendation, not a measured result.
Mark
And Flatpak KCM? Isn't that doing the same job?
Mimi
Not quite. It sits in KDE System Settings and handles XDG portal permissions: location, notifications, camera, screencasts. The article says Flatseal covers broader sandbox overrides.
Mark
What's the leftover data problem?
Mimi
Uninstalling doesn't necessarily remove what's in ~/.var/app/, like settings and caches. Warehouse finds and deletes that, and can snapshot apps before you change things.
Luke
The article doesn't say how much storage people typically recover. It says data can gradually consume space, but gives no figures.
Mark
Does the author claim these three cover everything?
Mimi
He says most desktop users won't need more, and names Flatsweep and jdFlatpakSnapshot for niche cases.
Luke
Again, that's his judgment. Nothing in the piece shows testing across different distros or setups.
O Pulso
- An image editor refuses to open a folder on another drive, and a media player cannot find external storage, stalling ordinary work.
- Sandboxing that protects users from stray access also blocks legitimate files and devices, leaving people puzzled why an app behaves differently from a traditional package.
- Flatseal lets users flip filesystem, device, and socket permissions for an app, then restart it to see whether the fix holds.
- On KDE Plasma, Flatpak KCM brings portal approvals into System Settings, letting users revoke old consents and tame repeated prompts.
- Warehouse tackles the storage backlog, clearing leftover data in ~/.var/app/ and offering snapshots, rollbacks, and update pinning to steady things again.
Anyone who has installed a Flatpak application and found it stubbornly unable to open a folder or see a connected drive has met a quiet tension in modern Linux: each app lives in its own sealed room, and its makers decide which windows open onto the rest of the house. How-To Geek's latest guide gathers three tools that let ordinary users reopen some of those windows, retrieve the clutter left behind by departed software, and step back in time when an update goes wrong. The author's judgment, offered as opinion rather than measured testing, is that these three will serve most desktop users well, leaving only niche problems to smaller helpers.
It starts with a small frustration: an image editor installed from Flatpak will not open a folder on another drive, or a media player cannot see the external disk plugged into the machine. The cause is the same each time. Flatpak runs applications inside isolated environments, and the developers decide which parts of the host system those applications may touch. That isolation is what lets one package work across many Linux distributions, but it also means the software can behave differently from what a traditional package would have done, and removing an app often leaves its settings and cached files behind, quietly consuming space.
How-To Geek's guide argues that most of these troubles can be handled by three tools rather than a scatter of utilities. Flatseal comes first, offering a plain interface for switching an app's access to files, devices, and system features on or off, with a reset option when something goes wrong. For KDE Plasma users, Flatpak KCM places portal permissions inside System Settings, covering things like location, notifications, camera, and screen sharing, and it can revoke approvals an app has remembered. The author suggests running it alongside Flatseal on Plasma, since each reaches a different layer of control.
Warehouse handles the cleanup and the safety net. It removes apps along with their stored data, finds leftovers from software already uninstalled, and can snapshot an app before a risky change so an earlier state can be restored. It also manages remotes, pins runtimes, rolls back updates where older versions exist, and masks apps that should not change. Flatsweep and jdFlatpakSnapshot remain worth knowing for narrower cases, but the author's verdict, given as opinion rather than tested benchmarking, is that these three will meet the needs of most desktop users.
Install an image editor from Flatpak, point it at a folder on another drive, and it may simply refuse to open. Install a media player and it may not see your external storage. These are the kinds of failures How-To Geek's latest Linux piece sets out to solve, and the cause is the same each time: Flatpak apps run inside isolated environments, and their developers decide which parts of the host system they can touch.
Flatpak makes it easier to install applications across different Linux distributions, but the sandboxing model that enables this has costs. An app may be unable to reach your files, recognize a connected device, or use a system feature. Permissions can also be stricter than what you would expect from a traditional RPM or DEB package. Removing an app brings a second problem: configuration files and other data can stay behind and keep taking up storage.
The author's argument is that you do not need a separate utility for every issue. Three applications, he writes, cover most of what goes wrong. The first is Flatseal, a graphical tool for changing an installed app's permissions. You pick the app, then switch access on or off for filesystem locations, devices, sockets, and other sandbox capabilities. The affected app must be restarted for changes to take effect, and Flatseal includes a reset option if something breaks. The author thinks it should be among the first utilities any regular Flatpak user installs, since it spares you from remembering individual flatpak override commands.
The second tool is for KDE Plasma users. Flatpak KCM is a configuration module that places Flatpak permission management inside Plasma's System Settings. It works with the XDG Desktop Portal permission system, covering location, notifications, screenshots, camera access, wallpaper changes, and other portal interactions. It can also manage certain remembered permissions, including screencast and remote desktop sessions. That helps when an app keeps asking for something you already approved, or when you want to revoke an earlier approval.
Flatpak KCM does not replace Flatseal. According to the article, the KCM focuses on portal permissions and related settings, while Flatseal offers broader control over sandbox overrides. On Plasma, the author suggests, running both gives you more room to troubleshoot an app that cannot reach a system resource.
The third tool, Warehouse, deals with cleanup. Flatpak normally stores application data in ~/.var/app/, including settings, caches, downloaded content, and other files an app creates. Keeping that data is handy if you plan to reinstall, but it can pile up as you try different software. Warehouse lets you inspect app information, uninstall apps, delete their stored data, and find leftovers from apps you have already removed.
It does more than tidy up. You can create snapshots of selected Flatpak apps to preserve their data before making changes, then manage those snapshots and restore an earlier state. You can browse and manage Flatpak remotes, add repositories, and install apps from different sources without a terminal or relying wholly on a software center. Warehouse can also roll back unwanted updates when an older version is available from the remote, pin runtimes to prevent changes, and mask apps to block updates.
The piece acknowledges these are not the only options. Flatsweep identifies and removes leftover files from uninstalled Flatpak apps, and jdFlatpakSnapshot offers another way to create and restore snapshots. The author considers them worthwhile for specific problems the main three miss, but believes most desktop users will find what they need in Flatseal, Flatpak KCM, and Warehouse. The article is an opinion piece, so that verdict is his judgment rather than a tested benchmark.
Citações Notáveis
Flatseal should be one of the first utilities you install if you regularly use Flatpaks, since it replaces remembering individual flatpak override commands.— How-To Geek author
Quer a matéria completa?
Leia o original em How-To Geek ↗