indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

[Gabor Toth]

The applet just crashed. ubuntu 11.10 upgraded from 11.04. it was very stable until now, suddenly appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Fri Dec 9 14:13:18 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0xe01ad1 <dbusmenu_menuitem_build_variant+401>: mov (%esi),%eax
 PC (0x00e01ad1) ok
 source "(%esi)" (0x0000000e) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 call_in_idle_cb (user_data=0x8a49690) at /build/buildd/glib2.0-2.30.0/./gio/gdbusconnection.c:4446
 g_idle_dispatch (source=0xb6855fc8, callback=0x872690 <call_in_idle_cb>, user_data=0x8a49690) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:4801
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (56 days ago)
UserGroups: adm admin audio cdrom dialout dip lpadmin netdev plugdev sambashare scanner vboxusers video

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