apparmor_parser crashed with SIGSEGV in __libc_start_main()

Bug #637681 reported by Pedro Miguel Baptista Machado
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apparmor

generated automatic

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apparmor 2.5.1~rc1-0ubuntu1
ProcVersionSignature: Error: [Errno 2] Ficheiro ou directoria inexistente: '/proc/version_signature'
Uname: Linux 2.6.36-999-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
Date: Tue Sep 14 00:54:23 2010
ExecutablePath: /sbin/apparmor_parser
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.36-999-generic root=UUID=3c197d48-5d8f-4a36-99be-d2798c937a98 ro splash vga=771 acpi_osi=Linux
ProcEnviron: PATH=(custom, no user)
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=4, ubp_av=0xbfe6e204, init=0x80da4e0, fini=0x80da4d0, rtld_fini=0xb7809b80 <_dl_fini>, stack_end=0xbfe6e1fc) at libc-start.c:226
 ?? ()
Title: apparmor_parser crashed with SIGSEGV in __libc_start_main()
UserGroups:

Revision history for this message
Pedro Miguel Baptista Machado (pedrmachado) wrote :
Revision history for this message
Pedro Miguel Baptista Machado (pedrmachado) wrote :

generated by so

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.