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.
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.