Bug 1019899 - Second zone Combo box shows wrong value
Summary: Second zone Combo box shows wrong value
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.5
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 15:14 UTC by Jiri Koten
Modified: 2017-12-05 13:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 13:03:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jiri Koten 2013-10-16 15:14:15 UTC 
Description of problem:
When I select Second zone in Evolution Preferences > Calendar, the combo box shows "None". But when I click on it Radio buttons show the selected time zone. Also the second zone is properly displayed in Calendar view.

And vice versa when I select None it shows the previously selected Time zone.

The time zone in Calendar is shown properly but the Combo box in Preferences shows wrong value, which can lead to confusion.

Version-Release number of selected component (if applicable):
evolution-2.32.3-30.el6

How reproducible:
100%

Steps to Reproduce:
1. Go to Calendar settings
2. Select Second time zone
3.

Actual results:
Combo box shows None

Expected results:
Combo box shows the selected Time zone

Additional info:
Comment 1 Milan Crha 2013-10-16 17:15:33 UTC 
I'm afraid this is due to some caching in GConf. I recall there was reported something like that in upstream, but never got addressed. I didn't investigate this yet, but the symptoms are basically the same, you see "old value" instead of current in the UI.
Comment 3 Red Hat Bugzilla Rules Engine 2017-12-05 13:03:58 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.