GNOME Bugzilla – Bug 740208
Time shifted after save and update from the server
Last modified: 2019-02-25 06:43:54 UTC
Hi, I've started having a new issue lately. Sometimes, my UWS calendar becomes read only. I get the following message: "Selected calendar is read only, thus cannot create event there. Select other calendar, please." This is just after I added a new entry. I'm really not sure if this is an Evo issue, or if it's a server issue, and I don't know how I to check. Another issue is that my appointments seem to shift by an hour. For example, I created an appointment for 330pm. After a while, it got shifted to 230 on it's own. There isn't a DST here at the moment. I've noticed this for a month now. Should I file a separate bug for this?
Screencast shows both issues: https://ankursinha.fedorapeople.org/gnome-bug740208/screencast.webm 1. Thing goes readonly 2. Events randomly shift - probably after a sync with the server. I already checked the regional settings on OWA - they're correct.
Thanks for a bug report. Let's deal with read-only at bug #721712 for the eds side, and with an evolution side here: Created commit e182db0 in evo master (3.13.9+) [1] Created commit 43601ac in evo evolution-3-12 (3.12.9+) It lefts this bug report for the time shift. [1] https://git.gnome.org/browse/evolution/commit/?id=e182db0
I see that Europe/Guernsey is mapped to "GMT Standard Time" Exchange (windows) time zone, which is just the Greenwich time, according to [2]. Do you know your Exchange server version, please? Do you know what timezone is set on the server (in the OWA interface)? I suppose you Evolution timezone is set to Europe/Guernsey too, as it is preselected in the Create Event dialog. You can run evolution-calendar-factory from a terminal as this: $ EWS_DEBUG=2 /usr/libexec/evolution-calendar-factory -w &>log.txt then wait a bit, until the initial update is over. After it reproduce the issue like in the video. Search the log for something unique, like the new event's summary or something like that. The output above and below it might be interesting, showing what timezone was used when the event was saved and what timezone was read. [2] http://msdn.microsoft.com/en-us/library/ms912391%28v=winembedded.11%29.aspx
*** Bug 740474 has been marked as a duplicate of this bug. ***
I'm setting this to need-info due to questions in comment #3.
My workaround for the time shift is to make every single appointment a recurring appointment for every 1 day with 1 occurrence. If I do so the time does not shift, not even on syncing with Exchange server.
(In reply to fbockstael from comment #6) > My workaround for the time shift is to make every single appointment a > recurring appointment for every 1 day with 1 occurrence. > If I do so the time does not shift, not even on syncing with Exchange server. What is your timezone settings in the Evolution (Edit->Preferences->Calendar Preferences) and on the EWS server, please? Do you know the server version, please? (like Exchange 2007, Exchange 2010, and so on; it can be seen in the EWS_DEBUG=2 log too (see the comment #3 above)).
(In reply to Milan Crha from comment #7) > What is your timezone settings in Evolution? Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment and if this still happens in a recent supported version. Thanks!