Ubuntu
memtest86+ package

on using " update-manager -d" and running upgrade from 8.04 to 9.10 the upgrade process failed with this error

Bug #445049 reported by raygj on 2009-10-07

This bug report is a duplicate of: Bug #408255: package_hook crashed with IOError in write(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	memtest86+ (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: memtest86+

fails to install the upgraded package "memtest86+" that you run from within the grub "select os to boot" menu that is used when you select "memory test (memtest86+)" . the upgrade program throws the "hook" error and stops the upgrade.

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 6 10:26:09 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=en_AU.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-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.31-11-generic x86_64
UserGroups:

Tags:

Revision history for this message

raygj (rayharlum-hotmail) wrote on 2009-10-07:

ApportLog.txt Edit (5.5 KiB, text/plain; charset="utf-8")
CrashReports.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (344 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (770 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-07: 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.