indicator-weather crashed with SIGSEGV in g_array_free()

[Jaydip Guha]

Indicator Weather crashes very often, since 12.10 days.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-weather 12.07.30-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
Uname: Linux 3.8.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 5 22:38:21 2013
ExecutablePath: /usr/bin/indicator-weather
InstallationDate: Installed on 2012-11-11 (114 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7f1e91d248b5 <g_array_free+21>: lock cmpxchg %ecx,0x18(%rdi)
 PC (0x7f1e91d248b5) ok
 source "%ecx" ok
 destination "0x18(%rdi)" (0x7f1e842fcb48) in non-writable VMA region: 0x7f1e842f0000-0x7f1e8430a000 r-xp /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.12
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4.0.12
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: Upgraded to raring on 2013-01-27 (37 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo 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 #1063643, 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.