apparmor_parser crashed with SIGSEGV in __libc_start_main()

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

Bug Description

Binary package hint: apparmor

apparmor crashed while updating today 9-10-10

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apparmor 2.5.1~rc1-0ubuntu1
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 2.6.36-020636rc3-generic x86_64
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: amd64
Date: Fri Sep 10 22:16:05 2010
ExecutablePath: /sbin/apparmor_parser
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.36-020636rc3-generic root=UUID=6e7cef07-99c8-40ba-b5f1-407e853643ed ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x40a14e: repnz scas %es:(%rdi),%al
 PC (0x0040a14e) ok
 source "%es:(%rdi)" (0x00000000) 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
Sharky (clhsharky) 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-amd64-retrace
Revision history for this message
Sharky (clhsharky) wrote :

Thank you

Sharky

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.