[Bug]: AppImage repeatedly requests AppArmor bootstrap despite installed AppArmor profile
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
The bootstrap check lives in the AppRun script, in the condition comparing $AA_PROFILE_PATH with the output of print_apparmor_profile. Start there and check whether the generated profile contains anything that varies between launches, such as the AppImage mount path. Done means a second launch with an already-loaded profile skips the root prompt. No test is mentioned, so you will need to reproduce on Ubuntu with AppArmor enabled.
Written by the indexing model from the issue text.
Description
Version
Version 0.13.6.1 (Official Build, Chromium 149.0.7827.200) appimage (64-bit)
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
- I have tried reproducing this issue in Helium with a new and empty profile using
--user-data-dircommand line argument and it could not be reproduced there
Description
The AppImage repeatedly requests AppArmor bootstrap authentication even though the AppArmor profile is already installed, loaded, and matches the generated profile.
How to Reproduce?
- Download the official Helium AppImage from https://helium.computer.
- Make it executable and launch it.
- Approve the AppArmor bootstrap authentication.
- Close Helium.
- Launch Helium again.
Sometimes Helium requests AppArmor bootstrap authentication again even though the profile already exists and is loaded.
Actual behavior
Helium requests root authentication again to execute:
- tee /etc/apparmor.d/helium-appimage
- chmod 644 /etc/apparmor.d/helium-appimage
- apparmor_parser -r /etc/apparmor.d/helium-appimage
The AppArmor profile is already present and loaded, so the bootstrap should not be necessary.
Expected behavior
After the AppArmor profile has been installed once, Helium should launch normally without requesting root authentication again.
Additional context
Environment:
• Ubuntu 24.04
• GNOME
• AppArmor enabled
• Official Helium AppImage
Investigation performed:
- /etc/apparmor.d/helium-appimage exists.
- The profile is loaded (verified with aa-status).
- The generated profile from AppRun matches the installed profile exactly (verified with diff).
- aa-enabled returns "Yes".
- /proc/sys/kernel/apparmor_restrict_unprivileged_userns is 1.
Looking at AppRun, the AppArmor bootstrap condition is:
! [ -f "$AA_PROFILE_PATH" ] ||
[ "$(print_apparmor_profile)" != "$(cat "$AA_PROFILE_PATH")" ]
However, the generated profile and the installed profile are identical, yet Helium still requests AppArmor bootstrap again on launch.
I have not yet tested with a fresh Helium profile (--user-data-dir) or other Chromium builds, as this issue appears to occur before the browser profile is used, during the AppImage AppArmor bootstrap.
The authentication dialogs request permission to run:
- tee /etc/apparmor.d/helium-appimage
- chmod 644 /etc/apparmor.d/helium-appimage
- apparmor_parser -r /etc/apparmor.d/helium-appimage
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days