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.
** Changed in: apparmor (Ubuntu)
Status: New = Confirmed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
** Summary changed:
- [Karmic] Apparmor does not allow the generation of new profiles
+ [Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the
existing profiles.
** Changed in: apparmor (Ubuntu)
Importance: Undecided = Medium
--
[Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the
existing profiles.
https://bugs.launchpad.net/bugs/446449
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
