Umm, I'm really trying to help here. Note that my patience is running thin, and I don't appreciate the patronizing tone. Here is what I've done to disable AppArmor on my system: sudo invoke-rc.d apparmor stop sudo update-rc.d -f apparmor remove After this, everything on my system works smoothly, including mysql. I don't need apparmor, so there is no point in trying to configure it, or to put it in complain mode, or whatever. I own this machine, therefore I and only I decide what can run on it and what can't. I decided to get rid of AppArmor. I do not want to disable any profile. I simply choose to not run AppArmor at all.
The repro steps are pretty simple. Once AppArmor is disabled (as per above), every update that wants to restart mysql fails, because it also starts AppArmor before that. Since AppArmor has never been configured on this machine, you can imagine that the defaults will break a lot of stuff. I asked that the update leave AppArmor alone, if it's stopped or disabled. It shouldn't be a big deal. It's not a problem for me anymore, since I removed the apparmor script from /etc/init.d, but perhaps it will help other people. This is about all the info I can provide. Thanks for your patience and help. -- package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/386867 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
