If you look at "sudo aa-status", I would expect that DHCP and CUPS are not
actually being confined by AppArmor, so there aren't errors. If you
restart the network or CUPS after starting AppArmor in the LiveCD, I would
expect those services to start failing. If that's _not_ the case, then
this should be examined further.
If you look at "sudo aa-status", I would expect that DHCP and CUPS are not
actually being confined by AppArmor, so there aren't errors. If you
restart the network or CUPS after starting AppArmor in the LiveCD, I would
expect those services to start failing. If that's _not_ the case, then
this should be examined further.