Controller.py crashed with IOError in debug()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| emesene |
Fix Released
|
Unknown
|
|||
| emesene (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: emesene
I started emesene, I tried to login and I got a failed login message: "Error during login, please retry (Connection problem)".
So far, so good. It may actually be a server/
But then the program crashed, and it shouldn't.
Using Ubuntu 8.04,
emesene version 1.0-dist-1
ProblemType: Crash
Architecture: i386
Date: Sun Apr 27 12:10:06 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.5
Package: emesene 1.0-dist-1
PackageArchitec
ProcCmdline: python /usr/share/
ProcEnviron:
PATH=/
LANG=it_IT.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: emesene
Title: Controller.py crashed with IOError in debug()
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video
| Danilo Piazzalunga (danilopiazza) wrote | #1 |
| Danilo Piazzalunga (danilopiazza) wrote | #2 |
| Changed in emesene: | |
| status: | Unknown → New |
| Changed in emesene: | |
| status: | New → Fix Released |
| Daniele Napolitano (dnax88) wrote | #3 |
| Changed in emesene (Ubuntu): | |
| status: | New → Fix Released |
This problem only happens if I have debug enabled and if I don't start emesene from a terminal.
I guess that debug() in emesenelib.common needs some error checking against failures to write on sys.stdout.
I have reported this bug upstream, too: http://