indicator-weather crashed with SIGSEGV

[João Antonio Santana]

Binary package hint: indicator-weather

Trying to manually update caused indicator to crash,

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.02.13+repack-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
Uname: Linux 2.6.38-4-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Feb 21 12:59:43 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=pt_BR:pt:en_GB:en
 PATH=(custom, user)
 LANG=pt_BR.UTF-8
 LC_MESSAGES=pt_BR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3796a56: movsbl (%eax),%eax
 PC (0x03796a56) ok
 source "(%eax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: indicator-weather crashed with SIGSEGV
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 icon_name_hash (key=0x1)
 find_image_offset (
 ?? ()

[Vadim Rutkovsky (roignac)]

This bug seems to related to setting some icon.
Is this still reproducible? If yes, please attach more logs - this would be of great help

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 551809, so it 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.