It looks as if you've made some configuration changes to bind9 (possibly
running chroot'ed) that are causing the app armour profile to fail when
bind9 is [re]started.
https://wiki.ubuntu.com/DebuggingApparmor has more information on
Apparmour failures.
Note, that the app armour profile for bind9
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
https://bugs.launchpad.net/bugs/684110
Title:
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.1 failed to install/upgrade:
sub-processo script post-installation instalado reto