indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

[Nicolas DERIVE]

Binary package hint: indicator-weather

Happening today with latest version of all programs. Crashed suddently with no particular action onto the indicator

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.04.10+repack-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
CrashCounter: 1
Date: Sat Apr 16 13:44:25 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/indicator-weather
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr_FR.UTF-8:fr:en_GB:en
SegvAnalysis:
 Segfault happened at: 0xb5f17be9 <dbusmenu_menuitem_build_variant+409>: mov (%esi),%eax
 PC (0xb5f17be9) ok
 source "(%esi)" (0x00000047) 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.3
 ?? () from /usr/lib/libdbusmenu-glib.so.3
 ?? () from /usr/lib/libdbusmenu-glib.so.3
 call_in_idle_cb (user_data=0x9459180) at /build/buildd/glib2.0-2.28.5/./gio/gdbusconnection.c:4427
 g_idle_dispatch (source=0x944fcf8, callback=0xb6e925d0 <call_in_idle_cb>, user_data=0x9459180) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:4545
Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()
UpgradeStatus: Upgraded to natty on 2008-10-18 (909 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video

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