indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

[Colin Keenan]

In alpha3 release of Ubuntu 12.10, indicator-weather frequently crashes, closing, and asking me to report this bug. So, now I'm reporting it. Looks same as bug #743541, but that is for Ubuntu 12.04.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-weather 12.07.30-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Thu Aug 30 21:27:37 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
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: 0xb547c249 <dbusmenu_menuitem_build_variant+329>: mov 0x0(%ebp),%eax
 PC (0xb547c249) ok
 source "0x0(%ebp)" (0x00000001) 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/i386-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()
UpgradeStatus: Upgraded to quantal on 2012-08-23 (7 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 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.