Created attachment 2517 possible fix Weather plugin may block on recv() forever* in some cases: it should be trivial to reproduce the bug with combination of laggy network & suspend-resume. Connection remains alive from kernel's point of view but no data comes and plugin deadlocks. I append possible patch fixing the issue for me, though it's rather ugly. See FIXME comment in the code. *) I waited for some hours.
I think this is what's happening today. Suddenly the plugin is totally dead. (Re)Adding it doesn't work, because the initial window is completely frozen. This is confirmed with other users that I asked on #xfce. Maybe it is when weather.com (or xoap.weather.com, which is unreachable today) has problems that the weather applet hardlocks. Please, we need this fix ASAP! My logs are filled with snippets like: (xfce4-weather-plugin:10344): weather-WARNING **: Unable to open image: /usr/share/xfce4/weather/icons/liquid/-.png (xfce4-weather-plugin:10344): weather-WARNING **: Unable to open image: /usr/share/xfce4/weather/icons/liquid/-.png (xfce4-weather-plugin:10344): weather-WARNING **: Unable to open image: /usr/share/xfce4/weather/icons/liquid/-.png libxfce4panel-Message: Weather Update: screen changed: 0 libxfce4panel-Message: No valid plug window. . . . if there is a deadlock as described above, that could certainly lead to the rest of the program not loading normally.
Same here with 0.7.3, stopped working half an hour ago. Cannot ping xoap.weather.com and the plugin freezes: - The existing one still works but shows no data, and freezes after entering the prefs dialog. - Adding a new instance doesn't work any longer because it freezes on initial configuration.
(In reply to comment #2) > - Adding a new instance doesn't work any longer because it freezes on initial > configuration. OK, it never really freezes, it is just unresponsive for a long time.
*** Bug 6057 has been marked as a duplicate of this bug. ***
Created attachment 2790 Fix very long update time I've solved this by applying the patch from comment #1 and setting update time to 60. However, I think this is not really a solution to this problem.
This bug has also been reported to Ubuntu Launchpad as: https://launchpad.net/bugs/546450 . Please advise if additional logs or backtrace is needed.
Is this still an issue? The FIXME in the code is still there, but does anyone actually experience any deadlocks? If so, is there some way to reproduce it?
It doesn't seem so. I haven't experienced any lockups anymore, and do hibernate/suspend and resume my machines a lot, therefore closing this long-standing bug now.