apparmor_parser crashed with SIGSEGV in __libc_start_main()

Bug #634479 reported by Ing0R
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apparmor

I have no idea.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apparmor 2.5.1~pre1393-0ubuntu6
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 2.6.36-020636rc3-generic 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
CrashCounter: 1
Date: Thu Sep 9 15:56:31 2010
ExecutablePath: /sbin/apparmor_parser
ProcCmdline: BOOT_IMAGE=/vmlinuz-2.6.36-020636rc3-generic root=/dev/mapper/g-r ro vga=0x361
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x8051044: repnz scas %es:(%edi),%al
 PC (0x08051044) 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 () from /lib/libc.so.6
 ?? ()
Title: apparmor_parser crashed with SIGSEGV in __libc_start_main()
UserGroups:

Revision history for this message
Ing0R (ing0r) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.