indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()

[Alex Mayorga]

Crash during "sudo apt-get upgrade".

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
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf5043a043813a33527c9f
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
CrashCounter: 1
Date: Mon Feb 20 14:50:41 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbde3f90b46 <dbusmenu_menuitem_get_children+22>: cmp %rax,(%rdx)
 PC (0x7fbde3f90b46) 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/x86_64-linux-gnu/libdbusmenu-glib.so.4
 dbusmenu_menuitem_build_variant () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 dbusmenu_menuitem_build_variant () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 call_in_idle_cb (user_data=<optimized out>) at /build/buildd/glib2.0-2.31.16/./gio/gdbusconnection.c:4698
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()
UpgradeStatus: Upgraded to precise on 2011-12-17 (64 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin netdev 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 #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.