kernel_crashdump crashed with OSError in <module>()

[Lance G.]

Binary package hint: apport

I'm not sure what this error/crash is but I was transferring a folder full of files using ssh when my computer just logged itself out and rebooted unexpectedly. There are many crash reports I will send with this same message because all these errors/crashes came up as a notification after reboot.

Computer Info

Computer: Acer Aspire One
Computer Type: Netbook(Sub-Laptop)
Computer Size: 8.9 inch
Computer Model: AOA150
Amount Of Computer Ram: 1024mb(1gb)
Amount Of Computer Storage: 122880mb(120gb)
Number Of Partitions On Computer: 4 (3 swap in a extended group totaling about 7gb, 1 ubuntu data partition totaling about 113gb)
Computer Operating System: Ubuntu 9.10 RC (updated from 9.04 about a week from this report) Plus add-ons: Ubuntu Studio, Kubuntu, and Xubuntu
Linux Kernel Used(if any): 2.6.31-14-generic

ProblemType: Crash
Architecture: i386
Date: Wed Oct 28 23:04:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/kernel_crashdump
InterpreterPath: /usr/bin/python2.6
Package: apport 1.9.3-0ubuntu4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/kernel_crashdump
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/share/apport/kernel_crashdump']
SourcePackage: apport
Title: kernel_crashdump crashed with OSError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/share/apport/kernel_crashdump", line 34, in <module>
     os.unlink(vmcore_path)
 OSError: [Errno 2] No such file or directory: '/var/crash/vmcore'
Uname: Linux 2.6.31-14-generic i686
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 #450295, 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.