Purging apparmor-profile-everything doesn't completely remove all the adjustments it has made

I installed apparmor-profile-everything on my Debian 12 machine for testing. It crashed my system. I purged the package but it still tries to run 4 profiles very early in the boot.

Dec 13 14:09:14 host kernel: audit: type=1400 audit(1702476554.403:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="systemd-shutdown" pid=861 comm="apparmor_parser"
Dec 13 14:09:14 host kernel: audit: type=1400 audit(1702476554.403:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="systemd-modules-load" pid=864 comm="apparmor_parser"
Dec 13 14:09:14 host kernel: audit: type=1400 audit(1702476554.407:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="systemd-sysctl" pid=867 comm="apparmor_parser"
Dec 13 14:09:14 host kernel: audit: type=1400 audit(1702476554.407:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="init-systemd" pid=872 comm="apparmor_parser"

It gives me this error in the first lines of the boot.log

$ cat boot.log
------------ Wed Dec 13 14:59:54 UTC 2023 ------------
/dev/mapper/host--vg-root: clean, 178104/1525920 files, 1905440/6103040 blocks
Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found
Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found
Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found
Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found

My other apparmor profiles still load. But that is later in the boot order

I cannot find what code tries to boot the profiles of apparmor-everything-profile so early. I searched for hours into grub and other files. How to fix this error? What file/code I need to look into?

Quote apparmor-profile-everything

Note: apparmor-profile-everything is still in development and breakage is likely. It is currently only recommended for developers.

Meaning: You’re on your own figuring this out and user support is unavailable.

Too much effort to document how to fix. I recommend a factory reset instead.

(Whonix is based on Kicksecure.)

Somehow it is gone after configuring LKRG. Not the cleanest fix :wink: