Marking this Invalid for now as using an Ubuntu kernel solved the issue.
** Changed in: apparmor (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036947
Title:
Looks like you have a non-standard kernel: 3.6.0-999-generic. This will
need to have the compatibility patches added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036947
Title:
[Quantal] rules
You're right Jamie, will comment with a genuine Quantal kernel on next
boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036947
Title:
[Quantal] rules not enforced, action reload failed
To
Booted with genuine 3.5.0.10 quantal kernel
feedback:
oem@dub:~$ sudo dpkg-reconfigure apparmor
* Starting AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
so the list is shorter.
--
You
That list is expected. Both firefox and rsyslog are installed but
disabled by default in Ubuntu:
https://wiki.ubuntu.com/Security/Features#apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
