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 526171 - Different temperatures shown in clock applet and its tooltip
Different temperatures shown in clock applet and its tooltip
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other All
: Normal minor
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 514333 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-04 15:37 UTC by lmEklxdMQh
Modified: 2008-04-07 19:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description lmEklxdMQh 2008-04-04 15:37:20 UTC 
Please describe the problem:
A different temperature is displayed in the tooltip of the intl-clock applet than in the applet itself.

Steps to reproduce:
1. In intl-clock applet, set location Norway/Trondheim/Vaernes as home
2. Hover mouse over weather symbol until tooltip appears


Actual results:
Tooltip and applet show different temperatures

Expected results:
Tooltip and applet show same temperature

Does this happen every time?
Only once have I seen it not happen over the last few weeks. Have tried setting other towns in same timezone as home, sometimes with same result(Kirkenes, Oslo, Copenhagen), sometimes not (Paris/Orly, Stockholm/Arlanda)

Other information:
Example: http://tihlde.org/~vidars/untitled.png
Comment 1 Vincent Untz 2008-04-07 11:38:04 UTC 
Do you have more than one location in your clock? If yes, then it could be because of bug 520212.
Comment 2 Vincent Untz 2008-04-07 17:22:58 UTC 
Hrm, no it seems it's a different bug.
Comment 3 Vincent Untz 2008-04-07 18:15:05 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 4 Vincent Untz 2008-04-07 19:25:30 UTC 
*** Bug 514333 has been marked as a duplicate of this bug. ***