> This is pending the changes requested in comment #7. The last time this app was confined with apparmor was in oracular, at version 3.5.4, and there it was using qt5. Now in plucky and later, it's using qt6, and has had a major version bump to 4.1.x, so the test plan needs to not only make sure the apparmor profile loads this time (which it is doing), but also that the app works fine while confined.
Is there an established way of documenting that a test of a GUI app has been done? I tested the fix in a LXD container (with all three releases, i.e. plucky, questing, resolute), and the app works with it as expected. But I'm not sure how to provide evidence of that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120284 Title: [SRU] Tellico AppArmor policy parser error: unexpected TOK_ID, expecting TOK_MODE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marble/+bug/2120284/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
