unkillable_shutdown crashed with OSError in orphaned_processes()

[bkadoctaj]

Binary package hint: apport

Happened on Ubuntu Lucid Alpha 3 for PowerPC on an eMac (USB 2.0).

apport:
  Installed: 1.13.1-0ubuntu1
  Candidate: 1.13.1-0ubuntu1
  Version table:
 *** 1.13.1-0ubuntu1 0
        500 http://ports.ubuntu.com/ubuntu-
        100 /var/lib/dpkg/status

Not sure what was supposed to happen, but after switching off Ubuntu and logging back in, this, along with some other bug notifications, appeared.

ProblemType: Crash
Architecture: powerpc
CrashReports:
 600:0:0:290301:2010-03-21 15:12:02.190381000 -0700:2010-03-21 15:12:03.190381000 -0700:/var/crash/_usr_lib_cups_filter_pstopdf.0.crash
 600:0:0:300407:2010-03-21 15:24:12.042381000 -0700:2010-03-21 15:24:13.042381000 -0700:/var/crash/_usr_sbin_cupsd.0.crash
 600:0:0:7763:2010-03-17 22:39:12.634536000 -0700:2010-03-21 15:24:48.426385877 -0700:/var/crash/_usr_share_apport_unkillable_shutdown.0.crash
 644:0:0:3882:2010-03-17 22:39:13.358540087 -0700:2010-03-17 22:38:42.890561045 -0700:/var/crash/_bin_mktemp.0.crash
Date: Wed Mar 17 22:39:13 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/apport/unkillable_shutdown
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha powerpc (20100315)
InterpreterPath: /usr/bin/python2.6
Package: apport 1.13.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/unkillable_shutdown -o 3356 -o 3362
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-16.25-powerpc
PythonArgs: ['/usr/share/apport/unkillable_shutdown', '-o', '3356', '-o', '3362']
SourcePackage: apport
Title: unkillable_shutdown crashed with OSError in orphaned_processes()
Uname: Linux 2.6.32-16-powerpc ppc
UserGroups:

[Apport retracing service (apport)]

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 #540436, 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.