Ubuntu
debsecan package

debsecan crashed with IOError in write()

Bug #214583 reported by wawadave on 2008-04-09

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

Affects		Status	Importance	Assigned to	Milestone
	debsecan (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

Binary package hint: debsecan

debsecan crashed with IOError in write()
crash happened well i was not near or on computer.

ProblemType: Crash
Architecture: i386
Date: Wed Apr 9 06:06:10 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/debsecan
InterpreterPath: /usr/bin/python2.5
Package: debsecan 0.4.10
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/debsecan --cron
ProcEnviron:
PATH=/usr/bin:/bin
LANG=en_US.UTF-8
SHELL=/bin/sh
PythonArgs: ['/usr/bin/debsecan', '--cron']
SourcePackage: debsecan
Title: debsecan crashed with IOError in write()
Uname: Linux 2.6.24-15-generic i686
UserGroups:

Tags:

Revision history for this message

wawadave (wawadave-gmail) wrote on 2008-04-09:

Dependencies.txt Edit (870 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (6.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (607 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (615 bytes, text/plain; charset="utf-8")

Revision history for this message

wawadave (wawadave-gmail) wrote on 2008-04-21:

crashes soon after systems started does this every time. today did it twice.
not sure what this does system works well other wise!

Revision history for this message

Daniel T Chen (crimsun) wrote on 2008-12-10:

Is this symptom still reproducible in 8.10 or 9.04?

Changed in debsecan:
status:	New → Incomplete

Revision history for this message

Hew (hew) wrote on 2008-12-23:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 124468, so it 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. Feel free to continue to report any other bugs you may find.