m4ko/pristontale-eu-linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 22 Wiki Activity

Added bubblewrap / apparmor fixes and diagnostic tools for troubleshooting it on related distros.

Browse Source
This commit is contained in:
m4ko
2026-09-03 22:16:43 +02:00
parent ecdea827ac
commit 5be4ace6c2
9 changed files with 1039 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
RELEASE_README.md
View File

@@ -57,6 +57,8 @@ pristontale-eu --help Show all commands and options
pristontale-eu gui Open the native dashboard
pristontale-eu doctor Check required host components
pristontale-eu runtime-bootstrap Prepare the verified UMU helper
pristontale-eu container-host Test the Bubblewrap sandbox
pristontale-eu container-host --repair Repair recognized Ubuntu AppArmor states
pristontale-eu login-diagnostics Check the login route without credentials
pristontale-eu login-diagnostics --runtime proton7
Compare the direct-Proton prefix read-only
@@ -84,4 +86,13 @@ pristontale-eu cache-compatibility PATH Cache a verified compatibility pai
```
Use `./install.sh --dry-run` to preview dependency installation or
`./install.sh --skip-deps` to manage distribution packages manually.
`./install.sh --skip-deps` to manage distribution packages and the host sandbox
manually.
On Ubuntu, install and launcher-update operations run a harmless Bubblewrap
user-namespace probe. If AppArmor produces the exact bwrap UID-map permission
denial, the launcher can install and load a pinned upstream restrictive bwrap
profile. It also repairs only UMU's known broken
`bwrap-userns-restrict-umu` link. Authentication is required; the repair does
not disable AppArmor or change global kernel security settings, and it refuses
to install a competing profile when another bwrap policy is present.