unkillable_shutdown crashed with AssertionError in add_proc_info()

Bug #544176 reported by muni
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

unkillable_shutdown crashed with AssertionError in add_proc_info()

ProblemType: Crash
ApportLog:
 apport (pid 5512) Mon Mar 22 13:48:15 2010: called for pid 5429, signal 11
 apport (pid 5512) Mon Mar 22 13:48:15 2010: executable: /usr/bin/nautilus (command line "nautilus")
 apport (pid 5512) Mon Mar 22 13:48:21 2010: wrote report /var/crash/_usr_bin_nautilus.1000.crash
Architecture: amd64
CrashReports:
 600:1000:1000:1223859:2010-03-22 13:50:00.000000000 +0000:2010-03-22 13:50:01.000000000 +0000:/var/crash/_usr_bin_nautilus.1000.crash
 600:0:0:10297:2010-03-22 13:27:26.000000000 +0000:2010-03-22 13:50:12.000000000 +0000:/var/crash/_usr_share_apport_unkillable_shutdown.0.crash
Date: Mon Mar 22 13:27:27 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/apport/unkillable_shutdown
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport 1.13.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/unkillable_shutdown -o 9348 -o 5549 -o 9349 -o 466
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/share/apport/unkillable_shutdown', '-o', '9348', '-o', '5549', '-o', '9349', '-o', '466']
SourcePackage: apport
Title: unkillable_shutdown crashed with AssertionError in add_proc_info()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: vboxusers

Revision history for this message
muni (liorviz) 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 #537904, 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.

tags: removed: need-duplicate-check
visibility: private → public
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.