There were two separate bugs affecting the start of the mysqld service after the switch from 5.5 to 5.6 (and to systemd from upstart or System V init at the same time, which was after my QA work and why this breakage went undetected before - sorry!).
This bug is about the AppArmor policy load problem, which is now fixed. The other issue is about the creation of /var/run/mysqld, which is on my list of things to look at and is now tracked in bug 1435823. There is a workaround available in that bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421303 Title: mysql does not import apparmor profile correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1421303/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
