After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 586167 - weather in clock is NEVER update after loss of connectivity
weather in clock is NEVER update after loss of connectivity
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: clock
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 614812 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-06-17 19:48 UTC by Hubert Figuiere (:hub)
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hubert Figuiere (:hub) 2009-06-17 19:48:02 UTC
Sunday I have had a long internet outtage (dead ADSL modem).

This has caused the weather in the clock to not update since. (we are Wednesday)
Comment 1 Pascal Terjan 2009-06-17 19:57:08 UTC
Confirming, this happens to me from time to time after my laptop is used offline
Comment 2 Callum McKenzie 2009-06-17 20:08:19 UTC
Clock applet bugs are handled by the gnome-panel product, not the gnome-applets product. Not that there is any easy way to figure this out.

In any event the bug has already been reported - complete with patch.

*** This bug has been marked as a duplicate of 579092 ***
Comment 3 Callum McKenzie 2009-06-17 22:08:33 UTC
Comments in 579092 suggest this is not a duplicate of that bug. Reopening and assigning to the correct product.

Comment 4 Fabio Durán Verdugo 2010-07-07 18:57:10 UTC
*** Bug 614812 has been marked as a duplicate of this bug. ***
Comment 5 Steve Chapel 2010-07-07 19:28:24 UTC
It should be easy to fix. Simply remember the time when the weather information was last downloaded, and do not display weather information if it is older than a few hours. There might be a problem if the system clock is changed by a large amount. This could cause the weather information to be removed prematurely if the clock is set forward, but this at least would not cause out-of-date weather information to be displayed. It could cause the weather information to be displayed for too long if the clock is set backward, although this problem could be minimized by always checking if the time of last weather download is past the current time, and setting it to the current time if it is.

I'd like to try to fix this. What would I do to get and build the source on Fedora 13? I tried looking through the documentation at gnome.org, but it doesn't seem to mention how to get the source and write patches.
Comment 6 Steve Chapel 2010-07-12 19:02:42 UTC
I was finally able to find the source code at http://git.gnome.org/browse/gnome-panel/ and http://git.gnome.org/browse/libgweather/

It seems that the problem is that libgweather effectively implements a cache of weather information, but does not have a policy for expiring out-of-date cache information (such as a DNS cache or browser cache). It maybe possible to implement the expiration policy I detail above by adding a field to store the time the weather information was retrieved to the _WeatherInfo struct, checking the time in the weather_info_is_valid method, and using that method instead of the valid field to check if the weather iformation is valid. This should fix the problem in all applications that use libgweather.

Now to figure out how to build and run libgweather...
Comment 7 Alex Marcotte 2010-08-06 07:08:52 UTC
I think I fixed this. Some info about building this to test would be greatly appreciated!
Comment 8 André Klapper 2020-11-06 20:21:44 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.