package_hook crashed with IOError in write()

[Detlef Lechner]

Binary package hint: apport

during dist-upgrading to 9.10

ProblemType: Crash
ApportLog:
 apport (pid 21014) Fri Oct 30 00:55:23 2009: called for pid 21013, signal 6
 apport (pid 21014) Fri Oct 30 00:55:23 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
 apport (pid 21014) Fri Oct 30 00:55:23 2009: Ignoring SIGABRT
Architecture: i386
CrashReports:
 600:0:0:176647:2009-10-30 06:50:01.000000000 +0100:2009-10-30 07:14:06.000000000 +0100:/var/crash/openoffice.org-emailmerge.0.crash
 600:0:0:11530:2009-10-30 07:18:11.000000000 +0100:2009-10-30 07:18:12.000000000 +0100:/var/crash/_usr_bin_landscape-sysinfo.0.crash
 600:0:0:6441:2009-10-30 06:01:43.000000000 +0100:2009-10-30 07:18:40.000000000 +0100:/var/crash/_usr_share_apport_package_hook.0.crash
 600:0:0:177331:2009-10-30 06:53:26.000000000 +0100:2009-10-30 06:16:35.000000000 +0100:/var/crash/openoffice.org-filter-binfilter.0.crash
Date: Fri Oct 30 06:01:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/package_hook
InterpreterPath: /usr/bin/python2.6
Package: apport 1.9.3-0ubuntu4
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/share/apport/package_hook -p openoffice.org-emailmerge -l /var/log/dist-upgrade/
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
PythonArgs: ['/usr/share/apport/package_hook', '-p', 'openoffice.org-emailmerge', '-l', '/var/log/dist-upgrade/']
SourcePackage: apport
Title: package_hook crashed with IOError in write()
Uname: Linux 2.6.28-16-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 #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.