Why Your “Secure” Flatpak App Can’t Open a Simple File
You’ve embraced the future of Linux applications: Flatpak. You love the security, the sandboxing, and the fact that you can get the latest version of GIMP or OBS Studio without messing with your system libraries. You launch your freshly installed app, try to open a file from your second hard drive… and… nothing. The app can’t see the drive. Or maybe your video editor can’t access your webcam, or your new text editor can’t access the network.
This isn’t a bug; it’s a feature. It’s the very “sandbox” you signed up for, working as intended.
Flatpak applications are isolated from your main system by design. They live in a container and are only given permission to access essential resources. To access anything else—like your ~/Downloads folder, a USB drive, or your network connection—they must be explicitly granted permission.
While this is fantastic for security (a rogue app can’t read your SSH keys), it can be incredibly frustrating for usability. For a long time, the only way to “fix” this was to use complex commands in the terminal.
This is the exact problem Flatseal was created to solve. If you use Flatpak, Flatseal isn’t just a utility; it’s an essential, non-negotiable part of your toolkit. In this guide, we’ll cover what is Flatseal and how you can use it to become the master of your app permissions.
What is Flatseal? Your Graphical Control Panel for Sandboxes
In the simplest terms, Flatseal is a graphical utility that allows you to review and modify the permissions for every Flatpak application installed on your system.
Instead of fumbling with flatpak override commands in the terminal, Flatseal provides a clean, two-pane interface:
- On the left, you see a list of all your installed Flatpak applications.
- On the right, you see a long, scrollable list of every possible permission for the application you’ve selected.
Each permission is presented as a simple on/off toggle or a text field. Want to give Kdenlive access to the network? Find “Network” and click the toggle. Want to allow GIMP to access your external hard drive? Scroll down to “Filesystem,” add the path, and you’re done.

It’s developed by Martin Abente Lahaye and is the de facto standard for this task, available directly from the main Flatpak repository. You can check out its official page on FLATHUB or its code on the FLATSEAL GITHUB REPOSITORY.
How to Install Flatseal on Your Linux System
Before you can manage Flatpak permissions, you first need to install Flatseal itself. There’s a high chance your distribution (like Fedora, Pop!_OS, or Linux Mint) already comes with Flatpak and the Flathub repository enabled.
If you’re unsure, or on a distro like Debian or Ubuntu where it might not be set up by default, first visit the official FLATPAK SETUP GUIDE and follow the two simple steps for your specific distribution.
Once Flathub is enabled, installing Flatseal is a single command:
Bash
flatpak install flathub com.github.tchx84.Flatseal
Pro-Tip: It is highly recommended to install Flatseal as a Flatpak itself (using the command above). While it might be available in some native repositories (like the AUR on Arch), the Flatpak version is the official release and is guaranteed to have the correct permissions to manage other Flatpaks.
After installation, you can launch Flatseal from your application menu just like any other program.
A Practical Walkthrough: How to Use This Flatseal Linux Guide
When you first open Flatseal, it might look a little intimidating, but the workflow is simple. Let’s break down the interface and the core process.
The Interface: Apps and Toggles
As mentioned, on the left, you’ll see your app list. You can also see “All Applications” at the top, which allows you to set global permissions that apply to every Flatpak. We’ll touch on that later, but for now, it’s best to manage permissions on a per-app basis.
Select an application, for example, GIMP.
On the right, you’ll see all its permissions. The most important categories are:
- Share: Controls access to shared resources, like the network (
Network), inter-process communication (IPC), or your system’s sound server (pulseaudio). - Socket: Governs access to system “sockets,” like the X11 windowing system (
x11), Wayland (wayland), or D-Bus. - Device: This is for hardware.
dri(for 3D acceleration/GPU),all(for webcams, controllers), andusbare common ones here. - Allow: Grants access to system-level features like Bluetooth (
bluetooth), running in the background (background), or viewing system processes (user-processes). - Filesystem: This is the big one. It controls which parts of your hard drive the app can see.
The “Changed” Indicator and the “Reset” Button
Two features make Flatseal incredibly safe and easy to use:
- The “Changed” Indicator: When you change any permission from its default state, a small “warning” triangle icon will appear next to it. This gives you an instant visual overview of what you have customized, making it simple to troubleshoot if an app suddenly breaks (or works!).
- The “Reset” Button: Did you toggle too many things? Did an app stop working? Are you worried you’ve created a security hole? Just select the app and hit the “Reset” button in the top-right corner. This will instantly revert all permissions for that specific app back to its original, developer-provided defaults.
The Golden Rule: Restart the App!
This is the #1 mistake new users make.
Permissions are NOT applied live. After you make a change in Flatseal, you must completely close and restart the target application for the new permissions to take effect.
Common Scenarios: How to Manage Flatpak Permissions in Real-Time
Let’s use this Flatseal Linux guide to solve the most common problems.
Scenario 1: Granting Access to a Specific Folder
- Problem: You installed GIMP (or any editor), and it can’t see your folder
~/Picturesor your external drive mounted at/mnt/Data. - Solution:
- Open Flatseal and select GIMP from the list.
- On the right, scroll down to the Filesystem section.
- You will see several toggles like
home,host, etc. DO NOT just turn onhome. This gives the app access to your entire home directory, which is often more than you want. - Instead, scroll to the bottom of the Filesystem section to find “Other files”.
- Click the “Folder” icon to the right and add the path to the folder you want, for example:
~/Pictures. - If you want to add an external drive, you may need to add its mount point, like
/mnt/Data. For removable USB drives, a common path to add isxdg-run/media, which gives access to the directory where modern systems mount removable media. - Close GIMP completely and re-open it. It will now see that folder.
Scenario 2: Disabling Network Access for an App
- Problem: You installed a simple calculator or note-taking app, and you’re paranoid. Why would it need internet access?
- Solution:
- Open Flatseal and select your Calculator App.
- Scroll to the Share section (it’s usually near the top).
- Find the “Network” toggle and turn it off.
- Restart the app. It is now completely offline, unable to send or receive any data.
Scenario 3: Enabling a Webcam or USB Device
- Problem: You installed Discord (or OBS Studio) as a Flatpak, and it says “No webcam detected.” Or you want a game to see your USB controller.
- Solution:
- Open Flatseal and select Discord.
- Scroll to the Device section.
- Turn on the
alltoggle (which often covers webcams) or, more specifically, look for ausbtoggle if available. - Restart Discord. Your webcam should now be available.
A Critical Warning: With Great Power Comes Great Responsibility
You now know what is Flatseal and how to use it. You also have the power to completely destroy the security model of Flatpak.
It can be tempting to “fix” all your problems by selecting an app and, under the Filesystem section, toggling on host.
DO NOT DO THIS.
Toggling filesystem=host gives the application full, unrestricted access to your entire root filesystem. It can see, read, write, and delete everything, including system files, other users’ home directories, and all your personal data. This completely defeats the entire purpose of using a sandboxed Flatpak.
Always follow the principle of least privilege. Only grant the minimum permissions an application needs to function. Don’t give an app access to your whole home directory if it only needs ~/Documents. Flatseal makes this granular control easy, so use it wisely.
The Missing Piece of the Flatpak Puzzle
Flatseal is an essential utility that bridges the gap between the high security of Flatpak and the practical usability we need for a daily-driver desktop. It transforms permission management from an obscure command-line task into a simple, visual, and safe process.
By understanding how to grant specific, limited permissions, you get the best of both worlds: secure, isolated applications that can still interact with your system exactly how you want them to.
What are your favorite or most-needed permission tweaks in Flatseal? Have you ever run into a strange permission issue that this tool helped you solve? Share your experiences in the comments below!
Disclaimer: Modifying permissions can affect application stability and system security. While using Flatseal is generally safe, granting excessive permissions (like filesystem=host) can expose your system to significant risks. Always grant the minimum permissions necessary and reset to default if you are unsure. Proceed at your own risk.

