GNOME Bugzilla – Bug 579434
not getting weather any more
Last modified: 2009-08-12 12:36:42 UTC
I have my gnome-panel/clock configured for a half-a-dozen "location"s but none of them are giving me weather any more. This used to work until not that long ago. I'm not sure what changed, although I am tracking Ubuntu Jaunty, so maybe some kind of regression has been introduced. I am quite good at trouble shooting and know programming, etc. but before I dive into the source and build debugging builds and so on, I'm wondering if there is any advice you can give on debugging this without having to dive into source and build printf sprinkled versions, etc.
I've also faced this two times now after changing login language.
(In reply to comment #1) > I've also faced this two times now after changing login language. Interesting. I didn't change login language or anything like that. How did you resolve it when it happened to you? I wonder if in my case, it has anything to do with my proxy configuration? It's worth noting that I don't see accesses to my proxy server even for weather info, so it seems that the requests for weather data are not even being made.
I think I resolved it by clicking around in the weather applet settings (Fahrenheit vs. Celsius and that stuff).
Alright. Got to the bottom of this one, however I will start off by saying I don't think it's resolved, I have just found the exact nature of the bug. The problem seems to be with regard to proxies. It seems that libsoup, which libgweather users, which is used by gnome-panel's clock/weather applet, cannot properly handle the "Automatic Proxy" type proxy setting. It can only handle "Manual". Given that Automatic is a valid setting in the proxy configuration, I consider gnome-panels inability (by way of libsoup) to use an Automatic Proxy a bug.
That all said, it would sure have been a lot easier to get to the bottom of this had gnome-panel actually reported the error back from libsoup. As it was, I ended up having to discover it in the debugger: Breakpoint 1, metar_finish (session=0x86ed370, msg=0x877c1a0, data=0x880fae0) at weather-metar.c:501 501 in weather-metar.c (gdb) print *msg $2 = {parent = {g_type_instance = {g_class = 0x8806510}, ref_count = 4, qdata = 0x0}, method = 0xb4c1b827 "GET", status_code = 3, reason_phrase = 0x8787450 "Cannot resolve proxy hostname", request_body = 0x880a800, request_headers = 0x86e4278, response_body = 0x880ab68, response_headers = 0x880acf0} Notice 'reason_phrase = 0x8787450 "Cannot resolve proxy hostname"'.
For me it doesn't work with any proxy setting (auto/manual, hostname/IP addr). It works correctly only when connected to a network that doesn't require to go through a proxy. Note that this problem affects both the clock applet and the weather applet version 2.26.1 (Ubuntu 9.04). Version 2.24.1 (Ubuntu 8.10, openSUSE 11.1) worked fine with or without a proxy.
This is also tracked on Launchpad: https://bugs.launchpad.net/bugs/372647 - exactly the same problem - with both applets - on 9.04 - using proxy
*** Bug 556371 has been marked as a duplicate of this bug. ***
I'm having the very same problem at my work place. I have to use a proxy and it used to work fine in Fedora 10, now that I installed Fedora 11 it doesn't work anymore. At home Fedora 11 works fine because I don't use a proxy there. I have to say that Firefox is configured to use the system's proxy settings and it works fine, so the gnome proxy configuration is working well. This bug is being tracked in RedHat's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=508168
As I reported in Red Hat's bugzilla, the last update fixed the problem for me: https://bugzilla.redhat.com/show_bug.cgi?id=508168#c4 Reporter, are you still having this problem?
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. This looks like a duplicate for bug #577532, which is fixed in libsoup 2.26.3, see: ftp://ftp.gnome.org/pub/gnome/sources/libsoup/2.26/libsoup-2.26.3.news *** This bug has been marked as a duplicate of 577532 ***