indicator-weather crashed with SIGSEGV in g_type_check_instance_cast()

[Chrescht]

I opened this new report because my Ubuntu and desktop are not the same.
I'm not running Unity but Gnome Classic (Gnome 2).

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-19.32-generic 3.0.27
Uname: Linux 3.0.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 10 15:34:44 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7fe80d91e56c <g_type_check_instance_cast+60>: movzbl 0x16(%r8),%eax
 PC (0x7fe80d91e56c) ok
 source "0x16(%r8)" (0x6c8948f0245c895e) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to oneiric on 2011-10-07 (185 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

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