I think I see this as well, simply doing an 'apt-get install mysql-server-5.6' on vivid leaves things in the following state after the installation completes:
$ sudo aa-status
[SNIP]
2 processes are unconfined but have a profile defined.
/usr/sbin/dnsmasq (665)
/usr/sbin/mysqld (9186)
which suggests that something is going wrong in the rats nest of mysql.postinst/invoke-rc.d. Is it possible that somehow the sysv init script /etc/init.d/mysql is getting invoked instead of the upstart job? (... as that script does not load the mysql apparmor profile before starting mysql, unlike the upstart job).
I think I see this as well, simply doing an 'apt-get install mysql-server-5.6' on vivid leaves things in the following state after the installation completes:
$ sudo aa-status sbin/dnsmasq (665) sbin/mysqld (9186)
[SNIP]
2 processes are unconfined but have a profile defined.
/usr/
/usr/
which suggests that something is going wrong in the rats nest of mysql.postinst/ invoke- rc.d. Is it possible that somehow the sysv init script /etc/init.d/mysql is getting invoked instead of the upstart job? (... as that script does not load the mysql apparmor profile before starting mysql, unlike the upstart job).