/sbin/apparmor_parser: ... Profile doesn't conform to protocol

This problem has already been reported for at least some of the packages involved.

The real issue is changes in the Linux kernel security model which, in turn, require a slightly different syntax for AppArmor rules. Those rules are not 100% compatible with those needed for 2.6.28 kernels used when upgrading from Jaunty.

This is a very common bug report, see e. g. bug 429863 or bug 429880.

Instead of trying to work arond this in a bazillion packages, is it possible to catch that situation in AppArmor itself and disable itself until the next boot into the karmic kernel?

I keep the other tasks open for now, but if it is possible to fix this centrally in apparmor, they can be invalidated.

Most packages either reload apparmor or call apparmor_parser -r "$APP_PROFILE".

This is a known issue and something that is being worked on. Assigning to John and will follow-up with him.

Based on converstion in #ubuntu-devel on IRC, this can and will be handled in apparmor. Invalidating the other bugs.

This bug was fixed in the package apparmor - 2.3.1+1403-0ubuntu23

---------------
apparmor (2.3.1+1403-0ubuntu23) karmic; urgency=low

  [ Kees Cook ]
  * Really fix quiet mode in initramfs (LP: #435285).
  * Handle older kernel versions when loading profiles (LP: #429872):
    - parser/parser_{interface,main}.c: detect kernel version and downgrade.
    - debian/apparmor.functions, parser/parser_main.c: keep kernel features
      recorded in cache directory.
    - parser/parser_{interface,main}.c: add --skip-kernel-load for testing.
    - parser/tst/caching.*: add caching tests.
  [ Jamie Strandboge ]
  * abstractions/audio: add a few more files for pulseaudio

 -- Kees Cook <email address hidden> Fri, 25 Sep 2009 09:54:01 -0700