This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu6
---------------
apparmor (4.1.0~beta5-0ubuntu6) plucky; urgency=medium
* Add patch for lsusb profile to access non-PCI USB info (LP: #2099990):
- d/p/u/lsusb_profile_fixup.patch
* Add patches to enable Python utils to skip profiles they can't parse
(LP: #2100744):
- d/p/u/0001-utils-read_profiles-robust-against-unparseable.patch
- d/p/u/0002-utils-test-minitools-resiliency-against-unparsed.patch
- d/p/u/0003-utils-remove-the-skip_-_profiles-testing-bypass.patch
* Add patch to fix fusermount3 profile breaking flatpaks (LP: #2100295)
- d/p/u/fusermount3-flatpak-fixup.patch
-- Ryan Lee <ryan....@canonical.com> Thu, 27 Feb 2025 14:45:18 -0800
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2100744
Title:
Fix parse failure that breaks aa-tools
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
The fix for https://bugs.launchpad.net/bugs/2100295 resulted in mount
rules in fusermount3 that caused all python aa-* tools to crash
because parsing of the new fusermount3 profile rules failed.
The this blocked merge of the fix for the fusermount3 profile in upstream
https://gitlab.com/apparmor/apparmor/-/merge_requests/1562#note_2371700197
This bug is to track the fix to the python aa-* tools such that a
failure to parse a profile won't cause the the tools to crash on all
policy.
Bug https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2100295
will track the fix to the fusermount3 profile.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2100744/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
