package_hook crashed with IOError in write()

Bug #445304 reported by Tenho Tuhkala
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

upgrading Jaunty -> Karmic by running update-manager -d

ProblemType: Crash
ApportLog:
 apport (pid 25487) Wed Oct 7 11:12:03 2009: called for pid 25486, signal 6
 apport (pid 25487) Wed Oct 7 11:12:03 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 25487) Wed Oct 7 11:12:03 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:6392:2009-10-07 11:35:40.505303000 +0300:2009-10-07 12:50:19.221809911 +0300:/var/crash/_usr_share_apport_package_hook.0.crash
 600:0:0:175041:2009-10-07 12:06:46.661304995 +0300:2009-10-07 11:35:23.113802481 +0300:/var/crash/memtest86+.0.crash
Date: Wed Oct 7 11:35:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/package_hook
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: apport 1.9.2-0ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/share/apport/package_hook -p memtest86+ -l /var/log/dist-upgrade/
ProcEnviron:
 PATH=(custom, user)
 LANG=fi_FI@euro
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.49-generic
PythonArgs: ['/usr/share/apport/package_hook', '-p', 'memtest86+', '-l', '/var/log/dist-upgrade/']
SourcePackage: apport
Title: package_hook crashed with IOError in write()
Uname: Linux 2.6.28-15-generic i686
UserGroups:

Revision history for this message
Tenho Tuhkala (muppis) 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 #427828, 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.