You are not logged in.
Managed to get apparmor setup using pacman a couple days ago and cleaned up /etc/apparmor.d directory to only contain profiles that I need, but then I just noticed that the default profiles returned back. If you are starting with apparmor its great to have these examples, but now its becoming a clutter.
Any way to persist configuration? I am not sure if it reverted because of pacman -Syu or because of something else.
Last edited by dab9966 (2025-04-20 20:33:59)
Offline
With the caveat that I have not looked deeply into apparmor configuration...
To prevent those files from being [re]installed, you could use the NoExtract option in your pacman.conf (or include file, if you use that), which can include shell-style glob patterns like /etc/apparmor.d/*
I was curious which ones are not owned by apparmor, and this showed a handful owned by firejail.
find /etc/apparmor.d -exec pacman -Qo {} \; | grep -v ' owned by apparmor '
Last edited by espresso (2025-04-20 16:02:37)
Offline
To prevent those files from being [re]installed, you could use the NoExtract option in your pacman.conf
Hello, thanks for responding.
I have updated the pacman.conf now, hopefully that was the issue and now it will be resolved.
I was curious which ones are not owned by apparmor, and this showed a handful owned by firejail.
find /etc/apparmor.d -exec pacman -Qo {} \; | grep -v ' owned by apparmor '
this shows majority of my profiles as unowned, for example error: No package owns /etc/apparmor.d/libreoffice. With few exceptions where it says is owned by libakonadi 24.12.3-1
.
I will mark the topic as solved for now, but will update if it occurs again.
Last edited by dab9966 (2025-04-20 20:22:15)
Offline