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 345021 - Weather Calendar shows incorrect information for today and tommorrow.
Weather Calendar shows incorrect information for today and tommorrow.
Status: RESOLVED DUPLICATE of bug 352287
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-15 15:30 UTC by Ryan P Skadberg
Modified: 2008-12-29 08:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Calendar showing Bad Weather (57.92 KB, image/png)
2006-06-15 15:34 UTC, Ryan P Skadberg
Details

Description Ryan P Skadberg 2006-06-15 15:30:38 UTC
It seems to me that my weather calendars always show 32 degrees for the current and next days and not the real weather information.

I have my calendar set up like this:

Type: Weather
Named: Boston Weather
Copy calendar contents locally is checked
Mark as default is unchecked
Location: Nother America : United States : Massachusetts : Boston
Units: Imperial (Fahrenheit, inches, etc)
Refresh: 30 minutes

Screenshot will be attached showing calendar with messed up information.
Comment 1 Ryan P Skadberg 2006-06-15 15:34:38 UTC
Created attachment 67427 [details]
Calendar showing Bad Weather

Forgot to mention this is:

EDS 1.7.2
Evo 2.7.2

I have seen this since at least 2.6, maybe even 2.4 if it had weather calendars
Comment 2 Poornima 2006-06-19 16:52:55 UTC
Reproducible in evo 2.6.x as well
Comment 3 Ryan P Skadberg 2006-07-17 18:56:27 UTC
Still seeing this in 2.7.4
Comment 4 Steven Willis 2007-02-13 19:16:31 UTC
Still seeing this in 2.8.1 (though I'm only seeing 32 degrees for the current day, it has "correct" numbers for tomorrow)
Comment 5 Matthew Barnes 2008-03-11 00:28:51 UTC
Bumping version to a stable release.
Comment 6 Akhil Laddha 2008-12-29 08:53:55 UTC
Patches from bug 352287 should solve it.

*** This bug has been marked as a duplicate of 352287 ***