indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()

[jrsutton]

Logged in and a crash report was waiting.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 5042392e7213102f5feb8218e75f2aa0
CheckboxSystem: edda5d4f616ca792bf437989cb597002
CrashCounter: 1
Date: Tue Sep 13 18:51:56 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
SegvAnalysis:
 Segfault happened at: 0x7f275eab2916 <dbusmenu_menuitem_get_children+22>: cmp %rax,(%rdx)
 PC (0x7f275eab2916) ok
 source "%rax" ok
 destination "(%rdx)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 dbusmenu_menuitem_get_children () from /usr/lib/libdbusmenu-glib.so.4
 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4
 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/libdbusmenu-glib.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (0 days ago)
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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #817672, 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.