GNOME Bugzilla – Bug 573866
Second time zone configuration window doesn't refresh immediately
Last modified: 2018-08-17 13:59:49 UTC
When you configure a second time zone for any location as a first time, tab (which display second time zone name), will still show you old time zone name.
Created attachment 129920 [details] Screenshot Like i have configured Berlin as second time zone. Now if i configure New York as second time zone, tab will still show me Berlin. But if i close configuration window and check again, it will show me New York which is right one.
Did you change the timezone in calendar day view while the configure tab was opened, or all done in configuration dialog only? If I recall correctly, I didn't add listening for change signal in the configuration dialog, because it didn't make much sense to change that value in the day view while having config dialog opened.
(In reply to comment #2) > Did you change the timezone in calendar day view while the configure tab was > opened, or all done in configuration dialog only? If I recall correctly, Yup, it happens when i change time zone (must condition - time zone should be selected first time) from calendar view. In mailer, it works fine.
I see this happening more often when I start with None second time zone set, and looking around showed that the gconf-client is returning old value the first time I ask for a change, but second and third attempt returns correct value. Bad thing I cannot reproduce this in a test application, only within evolution, but as far as I can tell, Evolution does nothing wrong, the sequence of commands is very simple: when clicking the timezone from a menu, in on_set_day_second_zone, I call calendar_config_set_day_second_zone which calls gconf_client_set_string Then, back in on_set_day_second_zone, is called update_day_second_zone_caption, which calls calendar_config_get_day_second_zone which uses gconf_client_get_string on the same config pointer as before, but returned old value, not that one set with gconf_client_set_string. I see this with GConf2-2.24.0-1.fc10.i386, but when I try to simulate the same in a test application it behaves like expected.
Wow, that button really needs to be a combo box...
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!