Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modifying app permisions breaks app build process #623

Open
2 tasks done
joshas opened this issue Oct 30, 2024 · 1 comment
Open
2 tasks done

Modifying app permisions breaks app build process #623

joshas opened this issue Oct 30, 2024 · 1 comment

Comments

@joshas
Copy link

joshas commented Oct 30, 2024

Checklist

  • 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

  1. Build flatpak application using flatpak-builder
  2. Run application and notice, that it is displayed among "Background Apps" in GNOME system menu
  3. 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 :)

@TingPing
Copy link
Member

TingPing commented Nov 14, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants