Page MenuHomeSolus

Possible Apparmor/Firejail profile bug
Closed, ResolvedPublic

Description

was asked to file this per @stalebrim at the forum.

On this thread https://discuss.getsol.us/d/6600-still-got-that-nagging-apparmor-problem/17, I provide anecdotal log evidence that soon after (minutes) an eopkg firejail install, my apparmor profiles became corrupt, thereby failing to load apparmor profiles for a week and leaving me vulnerable.

The last two log entries of that thread (

journalctl -xe
``` and

eopkg history

) is where we think we put 2 an 2 together..Since an eopkg rm firejail has cured this problem, I can no longer replicate, but thought it might be prudent to bring to your attention. Thank you.

Revisions and Commits

Related Objects

Event Timeline

my formatting went to heck, sorry

just to confirm that brent isnt crazy (not regarding this issue anyway), i had the same issue, removing firejail fixes it

This bug can be fixed by editing /etc/apparmor.d/firejail-default.

Just add:

#include if exists <tunables/run>

to the top of the file. Then run "sudo usysconf run -f" and "sudo systemctl start apparmor".

I hope this fix will be added to the next release.

This bug can be fixed by editing /etc/apparmor.d/firejail-default.

Just add:

#include if exists <tunables/run>

to the top of the file. Then run "sudo usysconf run -f" and "sudo systemctl start apparmor".

I hope this fix will be added to the next release.

Thanks for furnishing this. If this is not updated, I cut an paste your directions if I use firejail again down the road.

DataDrake triaged this task as Normal priority.Apr 22 2021, 10:28 PM
DataDrake edited projects, added Software; removed Lacks Project.
DataDrake moved this task from Backlog to Package Fixes on the Software board.
DataDrake added a subscriber: DataDrake.

This looks like an issue with the current version of firejail which likely needs an update.

as the OP, thank you to all involved for investigating and remedying. look forward to using this app again.