indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()

StacktraceTop:
 dbusmenu_menuitem_build_variant (mi=0x8985200, properties=0x89e3230, recurse=-1) at ../../libdbusmenu-glib/menuitem.c:1622
 bus_get_layout (server=0x8615088, params=0xb6a1ba00, invocation=0x89b6fb0) at ../../libdbusmenu-glib/server.c:1206
 bus_method_call (connection=0x84e2090, sender=0xb6a11bb8 ":1.83", path=0xb6a0db00 "/org/ayatana/NotificationItem/indicator_weather/Menu", interface=0xb6a0db40 "com.canonical.dbusmenu", method=0xb6a14810 "GetLayout", params=0xb6a1ba00, invocation=0x89b6fb0, user_data=0x8615088) at ../../libdbusmenu-glib/server.c:723
 call_in_idle_cb (user_data=0x89b6fb0) at /build/buildd/glib2.0-2.28.4/./gio/gdbusconnection.c:4427
 g_idle_dispatch (source=0xb6a101c8, callback=0x61b5d0 <call_in_idle_cb>, user_data=0x89b6fb0) at /build/buildd/glib2.0-2.28.4/./glib/gmain.c:4545

This one is going to need a valgrind log as it appears to be memory corruption. This value appears to be the problem:

        children = 0x234

There's no way children should be that value. If you run under valgrind it should give you some information on an invalid read or write happening.

crash on indicator weather ,utilized virtual box .

Occurred about five minutes after running upgrade in terminal. Weather indicator was not part of the upgrade. I am not sure it is connected. The system was sitting idle and the crash report came up.

Occured during idle time last night.

I have it on 11.10.

I have it on 11.10

I have it on 11.10

It occured to me last night again after not occurring for a bit. I have all the latest updates.

I get this randomly and fortunately it just happened while I had an strace running (attached). This time it occurred within a few seconds after switching the location from the indicator-weather menu.

I am switching now to running it with valgrind and will report the result whenever I get this to occur again.

Here's a valgrind report from a recent crash. I'm not sure though if it is the result of the same chain of events as above...

2 more and different valgrind logs. Crash frequency seems to be increasing...

Can confirm this on Ubuntu 11.10 64 bit.

crashed too in ubuntu 12.04 up-to-date 32bit

Also in 12.04 64 bit when resuming from suspend

These three valgrind logs all look more-or-less like this:

==1971== Invalid read of size 4
==1971== at 0x80A9804: PyObject_Free (in /usr/bin/python2.7)
==1971== by 0x80784F5: ??? (in /usr/bin/python2.7)
==1971== by 0x8112064: ??? (in /usr/bin/python2.7)
==1971== by 0x8112CB8: ??? (in /usr/bin/python2.7)
==1971== Address 0x44f2010 is 8 bytes inside a block of size 2,731 free'd
==1971== at 0x4027C02: free (vg_replace_malloc.c:366)
==1971== by 0x811709F: PyMarshal_ReadLastObjectFromFile (in /usr/bin/python2.7)
==1971== by 0x810FDCE: ??? (in /usr/bin/python2.7)
==1971== by 0x62696C2E: ???

It happened in Ubuntu 12.04. Can it be responsible also for bug https://bugs.launchpad.net/ubuntu/+source/unity/+bug/940603 ?
Because now I have this white box over the dash and the weather indicator crashed..

Just crashed with no reasons, 12.04 x64

Crashing here from time to time on 12.04 32 bit.

just crashed here, 12.04 64-bit, 3.2.0-29-generic kernel

Guys, Vadim left the project, I have no idea if somebody fix it ever

What a shame. Same specs as elhoir, indicator-weather has also been crashed for me lately. Does this mean the project is abandoned? Does Canonical know about this?

I have same bug on alpha3 release of Ubuntu 11.10

Crashed too - 12.04 x64

program crashed
lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
uname -a
Linux muletto01 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux

Does anybody (Canonical?) even try to fix this bug?
I'm running 12.04, which should be LTS and thus quite stable.
Unfortunately due this bug /home filled up, since it generated million lines of:

"(indicator-weather:2252): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_build_variant: assertion `DBUSMENU_IS_MENUITEM(mi)' failed"

to .xsession-errors file which ended up being size of 90G and then /home was full.

And as side effect of filled /home nobody was able to login to Unity after reboot. Luckily I had enough knowledge to use terminal and so on.

But due bugs like this it is very hard to recommend Ubuntu (Linux) as replacement of some other OS for people with less knowledge or interest to play with computers.

Osmo Laitinen, Indicator-Weather is third party application. It's not supported by Canonical. Do not expect someone from them to fix this bug. AFAIK the author of Indicator-Weather stopped development of the program. See description here: https://launchpad.net/weather-indicator

Crash in 13.04. But also in 12.10

The project is dead and bugs won't be fixed. If you check the project page the developer states this there. Sorry.

Also on 12.04.

Fix released? It just crashed on me so I'm not sure the fix really is released.

Ubuntu 13.04 64 bit

no Not fixed and now my system experiences a problem all the time!

On Sat, Jun 15, 2013 at 5:55 PM, Keith Clark <email address hidden>wrote:

> Fix released? It just crashed on me so I'm not sure the fix really is
> released.
>
> Ubuntu 13.04 64 bit
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1175152).
> https://bugs.launchpad.net/bugs/743541
>
> Title:
> indicator-weather crashed with SIGSEGV in
> dbusmenu_menuitem_build_variant()
>
> Status in DBus Menu:
> Incomplete
> Status in Indicator-Weather:
> Fix Released
> Status in “indicator-weather” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: indicator-weather
>
> This crash just appear.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: indicator-weather 11.03.20+repack-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
> Uname: Linux 2.6.38-7-generic i686
> NonfreeKernelModules: nvidia
> Architecture: i386
> CrashCounter: 1
> Date: Sun Mar 27 13:45:25 2011
> ExecutablePath: /usr/bin/indicator-weather
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
> InterpreterPath: /usr/bin/python2.7
> ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0xd69bb9 <dbusmenu_menuitem_build_variant+409>:
> mov (%esi),%eax
> PC (0x00d69bb9) ok
> source "(%esi)" (0x00000234) 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
> ?? () 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 natty on 2011-03-25 (2 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libdbusmenu/+bug/743541/+subscriptions
>

--
As always, K.M.

Ask Me how to get GMail!

What message do you get when it crashes? Just saying "it crashed on me" gives me no useful information with which to help you.

Please attach your ~/.cache/indicator-weather.log and the output of running the following commands in the terminal:
grep VERSION /usr/bin/indicator-weather
grep indicator-weather ~/.xsession-errors

Also, please try the latest unstable release, available from the PPA here:
https://launchpad.net/~weather-indicator-team/+archive/unstable

And let me know if the issue persists.

On trying to install from the unstable repo, I get:
"The following packages have unmet dependencies:

indicator-weather: Depends: python (< 2.8) but 2.7.4-0ubuntu1 is to be installed"

@ross

add this ppa

ppa:weather-indicator-team/ppa

sorry, this new one is better

https://launchpad.net/~pywapi-devel/+archive/ppa

On 13-06-18 02:56 AM, Joshua Tasker wrote:
> What message do you get when it crashes? Just saying "it crashed on me"
> gives me no useful information with which to help you.
>
> Please attach your ~/.cache/indicator-weather.log and the output of running the following commands in the terminal:
> grep VERSION /usr/bin/indicator-weather
> grep indicator-weather ~/.xsession-errors
>
keithclark@keith:~$ grep VERSION /usr/bin/indicator-weather
VERSION = "12.07.30 'Cloudy 10'"
         self.aboutdialog.set_version(VERSION)
     log.info("Weather Indicator version %s" % VERSION)

keithclark@keith:~$ grep indicator-weather ~/.xsession-errors
keithclark@keith:~$

elhoir: Thanks, that works!

Keith: you are using an extremely old version of Weather Indicator, please upgrade via the Weather Indicator Team PPA:
https://launchpad.net/~weather-indicator-team/+archive/ppa

Or from the downloads page:
https://launchpad.net/weather-indicator/+milestone/13.05.29

Why the need for a ppa I'm running 13.04 ubuntu?

What's wrong with the backports system?

Agreed. I'm running the latest 13.04 Ubuntu and am still getting weather-indicator 12.07.30 installed by default.

Because the latest version isn't in the official repo?

So, either install 13.06.01 manually, or get it from the PPA.