indicator-weather crashed with SIGSEGV in g_array_free()

[quequotion]

This is quite probably a duplicate of bug 827655.

My steps to reproduce are slightly different, so filing a new bug report.

Basically, this happens when there is no internet connection or no internet gateway in any connected network.

Steps to reproduce:

1. Disconnect PC from the internet
2. Log in
3. Observe (nearly) immediate crash of weather-indicator

OR:

1. Log in
2. Disconnect PC from the internet.
3. Observe somewhat delayed crash of weather-indicator.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Wed Feb 22 12:21:12 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7f294d7e7fb8 <g_array_free+24>: lock xadd %edx,0x18(%rdi)
 PC (0x7f294d7e7fb8) ok
 source "%edx" ok
 destination "0x18(%rdi)" (0x7f2943486c58) in non-writable VMA region: 0x7f294347b000-0x7f2943493000 r-xp /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.8
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.8
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 g_array_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/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_array_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #927384, 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.