GNOME Bugzilla – Bug 762949
switching an event to all day loses it's timezone
Last modified: 2017-11-24 21:42:27 UTC
When creating an event it gets a timezone (usually the local one). However setting it all-day sets the timezone to UTC, essentially losing the timezone information. Disabling all day then leaves the timezone unset and shifting the event by the timezone discrepancy.
Hi Marinus, this "feature" was added by this commit: https://git.gnome.org/browse/gnome-calendar/commit/?id=e5cd5ba7f5f8ef78dfdc4b9c64f85d3e1ba4d648 So, just to make sure, the problem is not when we change the timezone to UTC when user set all day event, but when it doesn't get back to local timezone when user unset it, right?
Well I guess you can see it that way, but the problem really is that when you change to UTC you already lost your original timezone info.
Created attachment 337911 [details] [review] edit-dialog: UTC timezone for all day events Timezone is being changed to UTC when user sets the event to be all day. Original timezone is then lost if user decides to set back to non all day event. This commit removes code responsible for changing timezone to UTC when editing an event using the edit dialog.
I tried this patch, but it hurts more than it helps; now every time a not-all-day event is edited, its times shift by the local time zone amount.
Review of attachment 337911 [details] [review]: We already discussed this issue on IRC (unfortunately lost the logs) and there's nothing we can really do. There's no way to store the previous timezone with libical.
*** Bug 779956 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/43.