mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2653] Error when running aa-enforce firejail-default #1673
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1673
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @julien-tmp on GitHub (Apr 15, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2653
I have the error below when running
aa-enforce firejail-default:Why does this happen and what to do about it?
@Vincent43 commented on GitHub (Apr 15, 2019):
What
sudo aa-statusshows?You may try
sudo apparmor_parser -r /etc/apparmor.d/firejail-defaultwhich is the recommended command for enabling apparmor profile referred in our manpage.@julien-tmp commented on GitHub (Apr 22, 2019):
Thank you for checking that @Vincent43
Here is the output:
and
It's possible that I have to do that:
https://ubuntuforums.org/showthread.php?t=2164641&p=12741691#post12741691
I don't want to play with grub too much in the following days. I will go back to this after making a backup.
PS: My partitions look like this if it helps
@chiraag-nataraj commented on GitHub (May 19, 2019):
@julien-tmp Did you ever revisit this?
@julien-tmp commented on GitHub (May 20, 2019):
Not yet unfortunately. Pretty busy lately. I will try to do it in this month. Do you face the same issue @chiraag-nataraj ?
@chiraag-nataraj commented on GitHub (May 20, 2019):
Nope, the apparmor integration is working fine on my end.
@Vincent43 commented on GitHub (May 20, 2019):
For some reason AppArmor isn't working on your system, this isn't firejail related.
@chiraag-nataraj commented on GitHub (May 21, 2019):
Yeah, looking over your earlier errors, this definitely looks like a non-firejail issue. @julien-tmp, the error looks like something that gets thrown when your kernel doesn't support apparmor. You'll have to look into possibly upgrading your kernel and/or figuring out why apparmor support seems to be disabled in your kernel.
Either way, this isn't a firejail issue, so I'll go ahead and close it, but feel free to keep replying and I'll do the best I can to help you figure it out :)