hrmm, well it seems I did fix this for unconfined processes before the final version of hardy (I remember fixing it for AppArmor 2.3 but I thought the fix missed Hardy), and my test machine wasn't properly updating. So after a fresh install MUGEN now works.
So to clarify, in Hardy MUGEN will run as long as it is started from an unconfined shell, and it does not have a profile defined for it. It is extremely unlikely that AppArmor in Hardy will be patched to support this behavior from a confined process. -- MUGEN doesn't start if Apparmor is running https://bugs.launchpad.net/bugs/190516 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
