deluge crashed with IOError in _print()
Bug #322910 reported by
spinstartshere
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Deluge |
Invalid
|
Unknown
|
|||
| deluge (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: deluge
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/deluge
InterpreterPath: /usr/bin/python2.5
Package: deluge-common 1.0.7.dfsg-3
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/deluge /tmp/MikeHancoc
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/deluge', '/tmp/MikeHanco
SourcePackage: deluge
Title: deluge crashed with IOError in _print()
Uname: Linux 2.6.28-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner vboxusers video
Revision history for this message
| spinstartshere (spinstartshere) wrote | #1 |
Revision history for this message
| Andrew Starr-Bochicchio (andrewsomething) wrote | #2 |
| Changed in deluge: | |
| status: | New → Incomplete |
Revision history for this message
| spinstartshere (spinstartshere) wrote | #3 |
Revision history for this message
| Andrew Starr-Bochicchio (andrewsomething) wrote | #4 |
| Changed in deluge: | |
| status: | Incomplete → Triaged |
| Changed in deluge: | |
| status: | Unknown → New |
| Changed in deluge: | |
| status: | New → Invalid |
| Changed in deluge: | |
| importance: | Undecided → Medium |
| status: | Triaged → Incomplete |
Revision history for this message
| Andrew Starr-Bochicchio (andrewsomething) wrote | #6 |
Revision history for this message
| Andrew Resch (andar) wrote | #7 |
| Changed in deluge (Ubuntu): | |
| status: | Incomplete → Fix Committed |
| Changed in deluge (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi,
Thanks for taking the time to report this bug and make Ubuntu better, but the report is lacking information that is need to track down this bug. Could you please tell us what you were doing when this error occurred? Are there steps that can be followed to reproduce it?
Thanks...