apparmor_parser crashed with SIGSEGV in __libc_start_main()

[Nicolas DERIVE]

Binary package hint: apparmor

I got this one updating to two latest versions of akonadi-server, seems a problem with apparmor invocation.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: apparmor 2.5.1~rc1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.36-1.7-generic-pae 2.6.36
Uname: Linux 2.6.36-1-generic-pae i686
ApparmorStatusOutput:
 Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set.
 apparmor module is loaded.
Architecture: i386
Date: Tue Nov 2 10:45:55 2010
ExecutablePath: /sbin/apparmor_parser
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.36-1-generic-pae root=UUID=57815366-c975-4e08-a10e-208025672f51 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr:en_GB:en
SegvAnalysis:
 Segfault happened at: 0x8051034: repnz scas %es:(%edi),%al
 PC (0x08051034) ok
 source "%es:(%edi)" (0x0000007b) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apparmor
StacktraceTop:
 ?? ()
 __libc_start_main (main=0x8050730, argc=5, ubp_av=0xbfeb8f94, init=0x80da4e0, fini=0x80da4d0, rtld_fini=0xb78c7ac0 <_dl_fini>, stack_end=0xbfeb8f8c) at libc-start.c:226
 ?? ()
Title: apparmor_parser crashed with SIGSEGV in __libc_start_main()
UserGroups:

[Apport retracing service (apport)]

Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced

[Sebastien Bacher (seb128)]

sorry natty bugs got cleaned wrongly

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #626984, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.