Red Hat Bugzilla – Bug 1024271
Free/Busy Information returns wrong time
Last modified: 2017-03-21 05:09:01 EDT
Description of problem:
When scheduling meeting, evolution can query Free/Busy time for meeting attendees. But it returns wrong time, it seems to be shifted by two ours in my case.
I'm using EWS backend and MS Exchange 2010 server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On first account create an appointment - make sure it shows time as busy
2. On second account schedule a meeting request with first account as required participant an choose the same time as the app. created in the first step
3. Query Free/Busy Time
It shows wrong time, doesn't show that the participant is busy at the given time
It shows that participant is busy
It was closed upstream recently. I do believe that Milan had this commit back ported to RHEL 6.5, as commit: ca3bb358ef5784450c930dcf8889e129eecc9461
Also, I think this bug is duplicated of #1018301
(In reply to Fabiano Fidêncio from comment #1)
> It was closed upstream recently. I do believe that Milan had this commit
> back ported to RHEL 6.5, as commit: ca3bb358ef5784450c930dcf8889e129eecc9461
> Also, I think this bug is duplicated of #1018301
Right, the upstream fix was added within evolution-exchange-2.32.3-15.el6, as part of bug #1018301.
(In reply to Jiri Koten from comment #0)
> When scheduling meeting, evolution can query Free/Busy time for meeting
> attendees. But it returns wrong time, it seems to be shifted by two ours in
> my case.
I see, the times are expected in UTC, thus there might be some issue with timezone correction.
Created attachment 822774 [details]
Because the Free/Busy is expected in UTC, but EWS' calendar backend has set other than that 'default_timezone', it applies the shift from UTC twice, once in the backend, the other time in the evolution's UI. RHEL7 (3.8.5) doesn't seem to be affected, same as 3.10/3.11 is not affected, because it doesn't change the backend's default_timezone anymore. I'll apply the change to 3.10/3.11 anyway, to have sources in sync.
Upstream commits in evolution-ews: a018dda on master (3.11.2+), 0416799 on gnome-3-10 (3.11.3+).
(In reply to Milan Crha from comment #3)
> RHEL7 (3.8.5) doesn't seem to be affected
Thinking of it, maybe you can clone the bug for rhel7 as well, if for nothing then to be sure and to have code in sync.
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.