weather applet freezes on clicking refresh

Please attach ~/.cache/indicator-weather.log file

I've attached the file now.

I guess, you've mistakenly attached an incorrect log -
'indicator_weather.log' is required

Oop sorry my mistake..Here is the proper file.

This bug is definitely related to the refreshing of the weather data. And this is becoming more and more annoying as I have do a hard restart of my system which is not good. I click on the weather indicator to see more weather info and if it is refreshing at that moment it freezes my system.

Please, attach the following logs - /var/log/syslog, /var/log/dmesg and /var/log/Xorg.0.log after the crash.
Mark the bug as Private (an edit button near 'This report is public') if these fiel should not be disclosed.

Can anybody else reproduce the same issue?

Hi, I tried to reproduce the bug and these are the steps that I took,

1. Change the weather provider to Google from Yahoo
2. Click the refresh button
3. Wait for a few seconds and then everything freezes according to the description provided before

I used the Yahoo weather provider and then clicked the refresh button, waited with the indicator menu open waiting for the program to update the refresh label in the hope that would cause a freeze but that did not happen. So I can conclude that something is wrong with the Google weather provider.

I hope you can reproduce this bug as well to understand the problem.

I have also attached the files that you requested in a .tar file. Hope this helps.

Found some interesting stuff in syslog:
Mar 16 14:35:43 krnekhelesh-Inspiron-1525 kernel: [ 3881.556565] plugin-containe[4210]: segfault at 20a41450 ip 20a41450 sp bfd7213c error 4 in libgtk-x11-2.0.so.0.2200.0[21993000+3c8000]
Mar 16 14:35:50 krnekhelesh-Inspiron-1525 wpa_supplicant[1552]: Failed to initiate AP scan.
Mar 16 14:35:51 krnekhelesh-Inspiron-1525 kernel: [ 3889.401622] nautilus[2231]: segfault at ffffffff ip 004b53cf sp bf81a4e0 error 4 in libgobject-2.0.so.0.2600.1[488000+41000]
Mar 16 14:35:52 krnekhelesh-Inspiron-1525 kernel: Kernel logging (proc) stopped.

Seems, that it is nautilus and plugin-container hanging up the system. Could not reproduce this on my machine, but it is clearly not the problem in Weather Indicator code, but something caused by Weather indicator / PyWAPI / threads handling code.

Mar 16 08:35:21 krnekhelesh-Inspiron-1525 kernel: [ 1589.867304] nautilus[2175]: segfault at ffffffff ip 006aa3cf sp bfd825d0 error 4 in libgobject-2.0.so.0.2600.1[67d000+41000]
Assigned to nautilus

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Nekhelesh, I guess, it is Flash ('plugin-containe' in syslog), that is freezing up the machine.
Could you please try refreshing Weather Indicator without Firefox running? If it works, try the same with Firefox on any plain HTML page (e.g. Google homepage)

I tried reproducing the error without Firefox running and it happens. Infact I just restarted the system and reproduced the error. But as I mentioned earlier it only happens when I choose Google as my weather data provider. Hence I am going to stick with Yahoo to be on the safe side. :)

And I'll do the crash report to nautilus.

This freezing has never happened before.. So yeah..

It seems to be reproducible for Maverick only. hope, this is related to previous libraries versions

The stall happens with Yahoo provider as well.
It happens when the user has the indicator menu popped up, while the program replaces the application-indicator menu (in menu_normal function (self.winder.set_menu(self.menu)).
Steps to reproduce:
- Choose Google as weather provider (it's slower than Yahoo, so it gives us time to reopen the menu, before the update occurs)
- Do a refresh
- Quickly reopen the menu; you'll see a "Refreshing please wait" in the refresh item.
- When the new weather data arrive, the gnome-panel will freeze.

Make sure to have a ssh session to your machine, opened from another machine, so that you can killall gnome-panel and escape from rebooting.
It's very possible that it happens with unity as well, I can't confirm it right now

If the menu is not shown during the replacement, there is no problem.
I think this bug belongs to either indicator-application or dbusmenu.
Somewhere on the client side, the gtk dbusmenu should get popped down, before it is released.

Vadim, a quick workaround/fix for this would be to set the indicator menu only once and only hide/show the items depending on the status.

It also happens with Unity and it is connected to the indicator label change as well.
The code in indicator-weather (line 989):
        self.winder.set_menu(self.menu)
        self.update_label("")

It replaces the menu while the menu is popped up and then resets the label to a zero sized string and this causes the freeze.

Adding a non-zero sized label fixes the problem:
        self.update_label(" ")

wow such a small thing causing a huge problem....but I understand the logic behind the problem. Hope this is fixed in the next release.

Such an elegant solution for the problem, thanks Panagiotis!

I think I might be seeing the same thing in gnome-terminal.

Jun 1 12:04:55 XXXX kernel: [364820.486296] gnome-terminal[3062]: segfault at 40e ip b70a96c0 sp bfe70f70 error 4 in libgobject-2.0.so.0.2600.1[b7080000+41000]

It happens sometimes when I close a window.

Might be the same thing affecting the gimp here: http://ubuntuforums.org/showthread.php?p=10887638.

I'm not all that sure what that most of that log line says. At the end I see "libgobject-2.0.so.0.2600.1[b7080000+41000]" I'm guessing those numbers show me a base location in memory where that library is loaded, and then +41000 is an offset. The combination of "libgobject-2.0.so.0.2600.1" and +41000 turns up in a number of error reports. Is there a way to find out what's going on in the library at +41000 ?

Considering this is only happening in Maverick in the comments, I'm going to assume that it got fixed in later versions. If I'm wrong, please reopen the bug. Also a stack trace would be really useful here. Thanks!