-
Notifications
You must be signed in to change notification settings - Fork 25
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
Issue after the last update (14.0) #364
Comments
Yes, I also get this issue using Debian stable. It appears to be the apparmor version on Debian isn't the most recent version. On Debian it's on the major version of 3, where as this profile is for version 4 which released about 7 months ago. Also version 4 isn't available in Debian Sid either. As Debian Bookworm was released in June 2023, I won't expect this to be present until the next stable version at the least sometime mid 2025, due to the feature freezes. Also this results in the SystemD Apparmor service failing. |
Linked issues on the Tor Project Gitlab for reference: |
I can confirm I could reproduce this in a Debian 12.8 VM.
Since I'm not very familiar with Apparmor, how does that manifest and what is the impact from a user perspective? |
Since the AppArmor profile is not useful on Debian stable (it's only
useful starting with Ubuntu 24.04 to enable user namespaces),
you can remove `/etc/apparmor.d/mullvad-browser` as a workaround.
I've opened
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41311.
|
Got this in my terminal after updating it today (18/11/2024):
I'm using the APT repository for Debian.
The text was updated successfully, but these errors were encountered: