tchx84
Clarify that Background permissions are a requirement for GNOME Builder (and flatpak-builder) to be able to compile the development version of an application
This UI here could benefit from a clarified explanation string:
"Can run in the background" is not really useful, mostly redundant with the name of the switch.
It would be more useful if, particularly for development versions of applications, it explained that it will be necessary for GNOME Builder (or flatpak-builder) to be able to compile the application if the user wants to compile it themselves. Otherwise the sandbox will kill it at random times during compilation, as you can see in https://github.com/flatpak/xdg-desktop-portal/issues/478
Without such a warning, users seeing an app's background permissions unexpectedly "soft-enabled" like that, in a seemingly non-default, state, may be tempted to turn off that permission, and then they spend hours debugging their build because of that issue.
hey @nekohayo , I am honestly not sure what to do here.
On one hand, I totally understand the frustration of getting your build killed seemingly out of nowhere due to toggling a random permission in GNOME Software, Flatseal or somewhere else.
On the other hand, there must be plenty of other strange side effects caused by toggling random permissions. Therefore, I struggle to see why there should be a warning for this particular scenario.
Perhaps this scenario should handled somewhere else (e.g, in GNOME Builder). Perhaps we should make it evidently more obvious that strange things can happen when random permissions are toggled.
Am I understanding correctly that even if the app UI is open and there is an open window, processes will be killed? Sorry if I'm misunderstanding this. But I wouldn't have expected a build process to be a "background process" if the app window is still open. That feels like a "foreground process" then.
