Fan of the layout and wanted to better understand the tool:
- For options that are unable to be turned off, is that because they are required by the app?
- For options that are unable to be turned off, If I select
OFF
for that permission, is that essentially a namespace/empty $HOME
to fulfill the app’s requirement?
is this question about an application or about how to configure flatpak permissions?
it’ unclear what tool you are referring to.
Whoops, I’m referring to the configuration of any/all Flatpaks using KDE’s Flatseal-equivalent app:
Flatpak permissions management KCM
Plasma System Settings module for managinng Flatpak permissions.
The System Settings module allows users to changing what permissions have
been granted to installed Flatpak applications.
1 Like
Typically yes, although global overrides also show as disabled check boxes. For example, I have global Flatpak environment overrides to make all apps respect my theme settings, so all of my applications’ Environment sections look like this:
Essentially yes.
On the Flatpak backend, it’s explicitly negating the package/global permission (e.g. setting filesystems=!xdg-desktop
if you set “xdg-desktop” to “OFF”). For most cases though, this has the same effect as you described.
1 Like