I'm a bit confused: * On the one hand, this bug is *not* marked is fixed in AppArmor upstream; the only reason it was marked as "Fix Released" for Ubuntu is the pile of kludges added in /lib/apparmor/functions, that I migrated to rc.apparmor.functions upstream a few years back.
* On the other hand, the aforementioned pile of kludges was removed by https://gitlab.com/apparmor/apparmor/-/commit/0b8ea047e88b250862da73a968b1cd1f8b7f6b91 because "LP:1377338 has been fixed for quite awhile". So, it seems to me that: * Either the parser bug was actually fixed upstream, and then the status this bug is incorrect: it should be "Fix Released". * Or the parser bug is still there, and then 0b8ea047e88b250862da73a968b1cd1f8b7f6b91 was done based on a misunderstanding. Which is it? -- 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
