After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 786154 - Editing time of event with unprefixed TZID strips time zone (converting it to floating time)
Editing time of event with unprefixed TZID strips time zone (converting it to...
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: General
3.24.x
Other Linux
: Normal major
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-08-11 13:29 UTC by Stephen
Modified: 2017-11-24 22:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stephen 2017-08-11 13:29:03 UTC 
Example:

On a system with a time zone of Europe/London (currently UTC+1, at time of this bug filing) an event with the following:

DTSTART;TZID=Europe/London:20170818T130000
DTEND;TZID=Europe/London:20170818T140000

is correctly displayed in Calendar as 13:00-14:00.

Editing the event in Calendar to change the time to 14:00-15:00 results in:

DTSTART:20170818T140000
DTEND:20170818T150000

I.e. the times have been changed to reflect the input values, but the time zone information has been stripped, resulting in a "floating time" event. Calendar also then immediately displays the floating time event incorrectly as well (treating it as UTC instead of local) - I'll file a separate bug for that.

An event with a TZID containing a registry prefix (for example Evolution) correctly retains the TZID after editing in GNOME Calendar. Example VEVENT fields:

DTSTART;TZID=/freeassociation.sourceforge.net/Europe/London:20170818T090000
DTEND;TZID=/freeassociation.sourceforge.net/Europe/London:20170818T093000
Comment 1 Georges Basile Stavracas Neto 2017-11-24 22:33:38 UTC 
-- 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/170.