Per user's comment, this was fixed in 8.10.
** Changed in: apparmor (Ubuntu)
Status: Confirmed = Fix Released
--
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
Looks like in Intrepid this bug is no more. Can we say fix released?
--
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
Thank you for the explaination. Now many things are clear :)
Just a thing that I don't have understood... can you please explain me what is
an unconfined shell and how to run it?
Thanks.
--
MUGEN doesn't start if Apparmor is running
https://bugs.launchpad.net/bugs/190516
You received this bug
well, I can confirm it, and even provide some insight.
MUGEN does some very uhm interesting things on startup. It creates a
new elf file in tmp, uses open to pin the file and then it deletes it.
This results in the file being removed from the namespace and completely
inaccessable except to
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
Ok, I have upgraded to Hardy Alpha6 (kernel 2.6.24-12-386), this bug still
persists.
Come on guys, there is someone that could download MUGEN and try to run it
using apparmor profiles? And that could set this bug as confirmed or
invalid or something different than incomplete?? :-)
--
MUGEN
** Changed in: apparmor (Ubuntu)
Status: Incomplete = Confirmed
--
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
Well, I don't remember well which kernel version I used, because for another
reason I had to format and reinstall Gutsy. It was, however, the Hardy alpha 4
kernel for 386 (2.6.24-something-386...).
In the link mentioned above there are all log entries. I'll write here briefly:
I have created a
