Comment 12 for bug 1231778

This is most likely due to the apparmor_parser errors. They are caused by having a new apparmor_parser, new policy (which now includes dbus rules), and old kernel.

The parser should be checking to see if the kernel supports dbus rules. Looking at the mount rule support in the parser,

* in parser/parser_main.c:get_match_string():
  - if apparmorfs/features/mount exists, the kernel_supports_mount global is set to 1
* in parser/parser_regex.c:post_process_mnt_ents():
  - mount rule entries are only processed if kernel_supports_mount is not 0
  - if kernel_supports_mount is 0, then a warning is emitted and the mount rule is ignored

The dbus rule support in the parser needs similar logic.