Comment 4 for bug 1691761

I did changes into aa-status (in line 148, as you mentioned above). This fixed the issue for me.

# aa-status
apparmor module is loaded.
1 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

I also tested it with loaded profiles (without default profile reload), and all looks good.

Is it possible to add some output like "N processes are confined by default profile." (with list of processes) or something like this in case of internal default profile detected? Or just warning, that default, non reloaded profile are used?