Thanks for helping to improve Ubuntu. At this point I think we're mainly aiming for a more complete bug report. Any work to "fix this" would come after that, once we have a clear, complete and reproducible bug report to work with.
(1) Please provide a complete set of steps to reproduce this issue, so that others (myself included) can duplicate it, as an important step in determining how best to solve it. Regarding following the documentation: (2) https://wiki.ubuntu.com/UsingAppArmor says: > Systems should not generally need to have AppArmor disabled entirely. > It is highly recommended that users leave AppArmor enabled and put > the problematic profile into complain mode (see above), then file a bug > using the procedures found in https://wiki.ubuntu.com/DebuggingApparmor. Was this documented approach followed? If so, which bug is the one you created following this procedure? Did this allows mysql-server to operate successfully on your system? What was the reason for your apparently highly exceptional need to completely disable AppArmor, against the clear recommendation in this documentation? (3) If for some reason putting this profile into complain mode did not help, https://wiki.ubuntu.com/UsingAppArmor also says that you can completely disable a specific profile (in this case the one for mysql server) by doing: sudo ln -s /etc/apparmor.d/profile.name /etc/apparmor.d/disable/ sudo apparmor_parser -R < /etc/apparmor.d/profile.name which in this case would become something like: sudo ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/ sudo apparmor_parser -R < /etc/apparmor.d/usr.sbin.mysqld Was this documented approach attempted? Was it successful in disabling the mysql-server apparmor profile and so allowing your mysql server to operate correctly? Are you in effect saying that the update to mysql- server undoes or reverses this change? So far, I have not been able to reproduce that behaviour here. Based on my (limited) testing here so far, this approach appears to work as documented, and it seems to leave the usr.sbin.mysqld profile disabled after the update. (4) Stating that "the apparmor profiles are bogus", and then failing to provide more specifics on this when requested to do so, seems somewhat unhelpful. Note that the README.Debian file included in this package says: If your system uses apparmor, please note that the shipped enforcing profile works with the default installation, and changes in your configuration may require changes to the installed apparmor profile. Please see https://wiki.ubuntu.com/DebuggingApparmor before filing a bug against this software. Ubuntu Jaunty 9.04 uses apparmor. Was this approach followed? -- 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 Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
