Ubuntu
computertemp package

computertemp crashes at random time

Bug #477367 reported by Cedric M on 2009-11-07

This bug report is a duplicate of: Bug #282899: computertemp crashed with IndexError in get_zone_temp(). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: computertemp

Never had any issue in Ubuntu 9.04.
After upgrade to 9.10, computertemp sometimes crashes (while not doing anything special).

ProblemType: Crash
Architecture: amd64
Date: Sat Nov 7 12:40:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-applets/computertemp
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: fglrx
Package: computertemp 0.9.6.1-1
PackageArchitecture: all
ProcCmdline: python /usr/lib/gnome-applets/computertemp --oaf-activate-iid=OAFIID:GNOME_ComputertempApplet_Factory --oaf-ior-fd=30
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/lib/gnome-applets/computertemp', '--oaf-activate-iid=OAFIID:GNOME_ComputertempApplet_Factory', '--oaf-ior-fd=30']
SourcePackage: computertemp
Title: computertemp crashed with IndexError in get_zone_temp()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Cedric M (cedric-m) wrote on 2009-11-07:

Traceback.txt Edit (786 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

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