Ubuntu
screenlets package

ClearWeatherScreenlet.py crashed with TypeError in show_error(): not all arguments converted during string formatting

Bug #718238 reported by Anton on 2011-02-13

This bug report is a duplicate of: Bug #420747: ClearWeatherScreenlet.py crashed with TypeError in show_error(). Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: screenlets

ClearWeatherScreenlet.py crashed with TypeError in show_error(): not all arguments converted during string formatting

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: screenlets 0.1.2-7ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
Date: Sun Feb 13 20:07:20 2011
ExecutablePath: /usr/share/screenlets/ClearWeather/ClearWeatherScreenlet.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python -u /usr/share/screenlets/ClearWeather/ClearWeatherScreenlet.py
ProcEnviron:
LANGUAGE=ru_RU:ru:en_GB:en
LANG=ru_RU.UTF-8
LC_MESSAGES=ru_RU.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/share/screenlets/ClearWeather/ClearWeatherScreenlet.py']
SourcePackage: screenlets
Title: ClearWeatherScreenlet.py crashed with TypeError in show_error(): not all arguments converted during string formatting
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Anton (welderx) wrote on 2011-02-13:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-14: 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 #420747, 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.