It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling of jobs doesn't stop with an error unless --abort-on-error is specified. Instead the parser will keep track of the last error and return that there was an error, but it will keep processing the rest of the jobs.
We did not close this for 3.0 as we wanted more time, to make sure we have it fixed. But we are considering it fixed on the dev branch. Though christian did turn up another corner case the other day https://gitlab.com/apparmor/apparmor/-/issues/215 that we need to finish fixing. ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #215 https://gitlab.com/apparmor/apparmor/-/issues/215 ** Changed in: apparmor Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377338 Title: apparmor may fail to load some profiles if one is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1377338/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
