feature: Support for snapped versions of Firefox and Chromium #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to Canonical's high-pressure selling of Snapcraft.
Snap in brief
Snap applies auto-generated AppArmor profiles located in
/var/lib/snapd/apparmor/profiles/. Profile template and data to populate the template.These profiles restrict access to
$XDG_RUNTIME_DIR(as reported in #247), and at the same time allow access to specific$XDG_RUNTIME_DIR's subdirectories, so$XDG_RUNTIME_DIR/snap.firefox/is accessible to snapped Firefox, and$XDG_RUNTIME_DIR/snap.chromium/is accessible to snapped Chromium.Browser profiles are located in
~/snap/$SNAP_INSTANCE_NAME/common/(~/snap/firefox/common/and~/snap/chromium/common/respectively).Possible solution
To comply with AppArmor restrictions mentioned above the in-memory part needs to be rerouted from the root of
$VOLATILEto respective subdirectories of it.Tested on Ubuntu 22.04.1 .