Red Hat Bugzilla – Bug 1264957
Changing weather calendar Units won't take effect until restart
Last modified: 2016-11-03 20:24:43 EDT
Description of problem: Currently changing Units in Properties of weather calendar take no effect until restart. The change is propagated either on the next start of the evolution-calendar-factory, or when the weather calendar is refreshed (which also involves the full close and open of it - multiple processes can have that backend open, that's why I mentioned the full close and open). Version-Release number of selected component (if applicable): evolution-3.12.11-15.el7 evolution-data-server-3.12.11-24.el7 How reproducible: 100% Steps to Reproduce: 1. Add new weather calendar 2. Select the calendar and open its Properties 3. Change Units to st. else. 4. Check your calendar Actual results: The weather calendars still shows old Units Expected results: Calendar properly updates Units Additional info:
It didn't work for the location changes too. I fixed it upstream for 3.19.1/3.18.1 with commit [1]. From the commit message: With this, either the Location or the temperature Unit change will cause refresh of the calendar and will show the values as being requested without require of the backend close and open. This is doing full refresh, aka talks to the server, thus it works only when being online. When being offline, or the weather server being unreachable, shows stale data anyway, thus it might be fine. The talk to the server also means that the change is not propagated immediately, but only after the server returns the data (there's a little lag). Thus please count with it. [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=a2235e4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2206.html