GNOME Bugzilla – Bug 71199
gweather doesn't work in two different networks
Last modified: 2004-12-22 21:47:04 UTC
GWeather seems to get stuck in an update loop, where the icon is a question mark, and the tooltip says "Updating...", and throws an error box when I right-click on it and tell it to update. The actual update hasn't happened in several hours, and there doesn't seem to be a way for my to cancel it.
I'm having the same problem. It happened immediately after starting the applet; I haven't seen it actually update once. :/ Marking as blocker because it is one; if there is no way to see the weather of any place other than Pittsburgh there isn't any reason to ship the applet.
I think the issue here is with respect to the "detailed update" option. The applet seems to take forever parsing the detailed forecast. I'm not sure why it seems to work in stable and not HEAD since the code hasn't really changed. I turned off the detailed forecast by default so an upgrade should fix this. This is maybe another reason to temporarily drop the forecast functionality for GNOME2
I was probably wrong about my previous analysis. This should be fixed in cvs. Joe, Luis does it work now?
Seems to be fixed for me. I haven't had the problem where it gets stuck for about a week or so. On a related note, though: the error message sucks. Why is it asking me a question? Why do I care if there is another update going? How would I check to see if there were, and how would I cancel it if there were? Why is it my responsibility to fix the problem, especially when it's set to auto-update and I didn't explicitly request an update? If there is another update going, why isn't the applet handling it correctly? That error message seems to be the error message it gives for every network error, even when it's wildly inaccurate... like when I have my network card unplugged from my laptop and it's failing because there's no DNS. Anyway, should I open another bug about the error message?
Joe: yeah, you should probably open a separate bug for that. Though, Kevin, if you are going to go ahead and remove the detailed forecast option, maybe Joe shouldn't waste his time...
Well, this is unrelated to the detailed forcast option. In fact, I never had that turned on now that I look at it.
Yah, file a bug about the update dialog - the applet really should stop the current update and do a fresh one instead of complaining. I looked into that, but it would be too much for the GNOME2 timeframe.
I tested on 10th-July build on solaris5.8, Still I am finding this bug. Ggweather gets stucks in an Update loop(by showing -17C). It gets updated only after logout and loging. It requires a session logout and login to get updated. this bug can be reopened.
Yeah, it's happening to me too. Also, does it do DNS caching or something? Because when I take my laptop to another network (ie, home) it never updates properly.
Joe: the applet uses gnome-vfs for the network stuff so any caching is due to gnome-vfs
May be related to bug #86631. Can you guys try out the patch attached to that bug?
This may be fixed in cvs. If someone could update and test, that would be great!
Kevin/Luis, can we move this to NEEDINFO state as the reporter is yet to respond on whether it is fixed for him.
I am testing the updated version now.
Joe: is this still happening ? If its is could you re-open and re-state exactly what's going on here? Thanks.
Okay, so originally the problem was as above; gweather would get stuck in this "updating" mode from which it would never recover, and I'd have to kill it. This seems to be fixed now. These days the only problem I have with it is when I try to update from a different location. It works fine from work, but if I take it home and try to update it, it doesn't. It has the "Updating..." tooltip for a while, and then has the "Retrieval failed" tooltip. It has the "? --" display the whole time. If I kill it and restart it, it works at home, and I run it on a desktop I have here at home, so it's not my network topology here. Might gnome-vfs be caching DNS servers or something along those lines? They change between locations. Since this only seems to be a problem on laptops, the severity/priority can probably be knocked down.
Yah, probably gnome-vfs caching DNS or something. We should probably move this to gnome-vfs. Joe: see if this happens to stock-ticker also. They both use gnome-vfs
Looks like what is left of this is covered in 76283, AFAICT. *** This bug has been marked as a duplicate of 76283 ***