indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

[Jeroen T. Vermeulen]

Automatically reported crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 11.11.28-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
CrashCounter: 1
Date: Sun Mar 18 13:59:20 2012
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=en_US:en
 LC_TIME=en_DK.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5c70df1 <dbusmenu_menuitem_build_variant+401>: mov (%esi),%eax
 PC (0xb5c70df1) ok
 source "(%esi)" (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 precise on 2012-01-14 (63 days ago)
UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin netdev plugdev pulse pulse-access sambashare 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.