Ubuntu
screenlets package

SysmonitorScreenlet.py crashed with TypeError in on_draw()

Bug #468442 reported by Wayazaexa on 2009-11-01

This bug report is a duplicate of: Bug #238841: [Sysmonitor] SysmonitorScreenlet.py crashed with TypeError in on_draw(). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: screenlets

1) 9.10

2) 0.1.2-7

3-4) I wasn't really expecting anything, as far as I know I had nothing to do with screenlets, it just broke down.

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 13:22:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/screenlets/Sysmonitor/SysmonitorScreenlet.py
InterpreterPath: /usr/bin/python2.6
Package: screenlets 0.1.2-7
PackageArchitecture: all
ProcCmdline: python /usr/share/screenlets/Sysmonitor/SysmonitorScreenlet.py > /dev/null
ProcEnviron:
LANGUAGE=en_GB.UTF-8
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-12.43-netbook-eeepc
PythonArgs: ['/usr/share/screenlets/Sysmonitor/SysmonitorScreenlet.py', '>', '/dev/null']
SourcePackage: screenlets
Title: SysmonitorScreenlet.py crashed with TypeError in on_draw()
Uname: Linux 2.6.28-12-netbook-eeepc i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags:

Revision history for this message

Wayazaexa (jocke-englund) wrote on 2009-11-01:

Traceback.txt Edit (381 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.8 MiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-05: 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 #238841, 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.