indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_id()

StacktraceTop:
 dbusmenu_menuitem_get_id (mi=<value optimized out>) at /build/buildd/libdbusmenu-0.4.0/./libdbusmenu-glib/menuitem.c:518
 menuitem_property_idle (user_data=<value optimized out>) at /build/buildd/libdbusmenu-0.4.0/./libdbusmenu-glib/server.c:940
 g_main_dispatch (context=0x1835f10) at /build/buildd/glib2.0-2.28.4/./glib/gmain.c:2440
 g_main_context_dispatch (context=0x1835f10) at /build/buildd/glib2.0-2.28.4/./glib/gmain.c:3013
 g_main_context_iterate (context=0x1835f10, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./glib/gmain.c:3091

I think we're going to need a valgrind log on this one as well. I've checked to ensure that we're referencing all the objects being used and that all looks good. So something fishy has to be going on. Thanks!

How do I get a valgrind log for the indicator?

you should be able to run it under valgrind on a command line? see https://wiki.ubuntu.com/Valgrind for details on valgrind

Two question: indicator-weather is launched on login. Should i kill the running process and then run indicator-weather with valgrind? indicator-weather crashes very rarely and I don't know how to trigger it. Is it useful to run valgrind on indicator-weather, when indicator-weather will crash in x hours (or y days)?

you can stop the running instance and start a new one under valgrind yes, run it until you get an "invalid read" or "invalid write" in the valgrind log, better to install the debug packages before starting to the log you get is an useful one

indicator-weather neither have a debug package nor a ddeb.

indicator-weather is a python script which explains why there is no ddeb for it.

I ran indicator-weather with valgrind. It hasn't crashed yet, but it shows some backtraces on the terminal:

Exception in thread Fetcher:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/bin/indicator-weather", line 1148, in get_new_weather_data
    weather = self.get_weather()
  File "/usr/bin/indicator-weather", line 1211, in get_weather
    return self.current_location.weather
AttributeError: Location instance has no attribute 'weather'

right, but you should install the ddeb for the libraries listed in the stacktrace if you can that's likely those that will show in the log

I fail to reproduce this crash.

I wonder if this might be linked to connectivity? For me it crashed when I joined a pay for wireless network which required web based user/password credentials. So while the applet had network access, all lookups for weather updates etc would have failed and delivered it "corrupted" information.

It just seemed like too much of a co-incidence.

By the way, this was on fully updated 11.10.

I just got this on up-to-date Ubuntu 12.04.

Mark, was the stacktrace the same?

Charles, the duplicate report I've just filed contains an amd64 stack trace for precise. HTH.

This was an issue with Weather Indicator's threading code; it has since been rewritten, and should no longer exhibit this behavior.

However, if there is an underlying dbus issue, it has not been addressed -- I know this crash usually occurred (albeit sporadically) when updating the menu from a thread other than the main thread.