unkillable_shutdown crashed with AssertionError in add_proc_info()

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

Bug Description

Binary package hint: apport

I think I might have pressed the power down button. When a certain mount point was not reading during shut down.

ProblemType: Crash
ApportLog:

Architecture: i386
CrashReports:
 600:1000:1000:421923:2010-03-14 14:44:36.066015000 -0400:2010-03-14 14:44:37.066015000 -0400:/var/crash/_usr_lib_gnome-disk-utility_gdu-notification-daemon.1000.crash
 600:0:0:7488:2010-03-16 12:30:32.341032000 -0400:2010-03-17 07:49:57.557910760 -0400:/var/crash/_usr_share_apport_unkillable_shutdown.0.crash
 600:0:0:6692:2010-03-14 14:46:44.186018000 -0400:2010-03-14 14:46:45.186018000 -0400:/var/crash/_bin_mount.0.crash
 600:1000:1000:145616:2010-03-14 14:48:24.026015000 -0400:2010-03-14 14:48:25.026015000 -0400:/var/crash/_usr_lib_gvfs_gvfs-gdu-volume-monitor.1000.crash
Date: Tue Mar 16 12:30:33 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/apport/unkillable_shutdown
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100310)
InterpreterPath: /usr/bin/python2.6
Package: apport 1.13-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/unkillable_shutdown -o 678 -o 266 -o 270 -o 267
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/share/apport/unkillable_shutdown', '-o', '678', '-o', '266', '-o', '270', '-o', '267']
SourcePackage: apport
Title: unkillable_shutdown crashed with AssertionError in add_proc_info()
Uname: Linux 2.6.32-16-generic i686
UserGroups:

Revision history for this message
wrabacon (wrabacon) 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.