Ubuntu
indiv-screenlets package

SysmonitorScreenlet.py crashed with IndexError in get_variables(): list assignment index out of range

Bug #850932 reported by Gustavo on 2011-09-15

This bug report is a duplicate of: Bug #748846: SysmonitorScreenlet.py crashed with IndexError in get_variables(): list assignment index out of range. Edit Remove

This bug affects 1 person

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

Bug Description

I ghet lot of crash wornings and I cant close screenlet any more

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: screenlets-pack-all 0.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 15 15:43:37 2011
ExecutablePath: /usr/share/screenlets/screenlets-pack-all/Sysmonitor/SysmonitorScreenlet.py
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python -u /usr/share/screenlets/screenlets-pack-all/Sysmonitor/SysmonitorScreenlet.py
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/share/screenlets/screenlets-pack-all/Sysmonitor/SysmonitorScreenlet.py']
SourcePackage: indiv-screenlets
Title: SysmonitorScreenlet.py crashed with IndexError in get_variables(): list assignment index out of range
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Gustavo (paolo-nino) wrote on 2011-09-15:

Traceback.txt Edit (475 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-19: 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 #850965, 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.