You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a bug that matches the one I want to file, without success.
flatpak-builder version
1.4.1
Flatpak version
1.15.10
How to reproduce
Build flatpak application using flatpak-builder
Run application and notice, that it is displayed among "Background Apps" in GNOME system menu
Go into "Settings" -> "Apps" and remove "Run in Background" setting for this application.
Expected Behavior
Permissions should not interfere with application build.
Actual Behavior
flatpak-build stops with error message:
clang++ "Child process exited with code 137"
Additional Information
If custom permission settings might interfere with build, flatpak builder should inform about that before build.
If this is something by design, I would like to know explanation, why this happens, just to satisfy my curiosity :)
The text was updated successfully, but these errors were encountered:
I have not looked at this in depth but the process management is not done by flatpak-builder or flatpak, so I think this should be reported elsewhere (xdg-desktop-portal?). flatpak build explicitly includes information in the manifest that it is a build environment and not running an app. The process that checks for this permission could check that.
It is possible something should be changed here to never use the app id, but I'm not sure offhand.
Checklist
flatpak-builder version
1.4.1
Flatpak version
1.15.10
How to reproduce
Expected Behavior
Permissions should not interfere with application build.
Actual Behavior
flatpak-build stops with error message:
clang++ "Child process exited with code 137"
Additional Information
If custom permission settings might interfere with build, flatpak builder should inform about that before build.
If this is something by design, I would like to know explanation, why this happens, just to satisfy my curiosity :)
The text was updated successfully, but these errors were encountered: