I can reproduce the problem on Karmic. Once you've generated a profile with aa-genprof, aa-logprof will parse the log files properly.
If you restart apparmor "/etc/init.d/apparmor restart", aa-logprof will ask for confirmation on every log entry it finds and will break the profile.
I'll investigate this.
I can reproduce the problem on Karmic. Once you've generated a profile with aa-genprof, aa-logprof will parse the log files properly.
If you restart apparmor "/etc/init. d/apparmor restart", aa-logprof will ask for confirmation on every log entry it finds and will break the profile.
I'll investigate this.