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 728219 - gweather shows time of last update as UTC
gweather shows time of last update as UTC
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: gweather
2.10.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-14 21:55 UTC by Stéphane Aulery
Modified: 2014-04-15 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stéphane Aulery 2014-04-14 21:55:25 UTC 
Reporter from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319471

Currently gweather seems to show time of last update as UTC. 
It would be more appropriate to have local time of the specified location instead.

Local time under 'Last update', 'Sunrise' and 'Sunset' are good, but
'local time' is relative to what you call local. 

For instance, I have an Eindhoven and a Reykjavik applet, which have
different local times, but which one is shown by the applet? Judging
from the values I would say local time of the computer, but that looks
strange for the other applet (sunset in Reykjavik at 22:34??).

Maybe the times for both timezones should be shown if they differ.
Comment 1 André Klapper 2014-04-15 13:13:56 UTC 
You are using version 2.10.x which is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that older version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

Please feel free to reopen this bug if the problem still occurs with a recent version of GNOME, or feel free to file a bug report in the bug tracking system of your Linux distribution if your distribution still supports your version 2.10.x

(I don't see much sense in forwarding eight year old bug reports to upstream without any indicators that this is still a problem in GNOME 3.x or at least 2.32.)