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 579561 - Evolution fails to include VTIMEZONE in .ics file
Evolution fails to include VTIMEZONE in .ics file
Status: RESOLVED DUPLICATE of bug 543069
Product: evolution
Classification: Applications
Component: Calendar
2.26.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-04-19 22:20 UTC by John Haiducek
Modified: 2009-05-25 21:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description John Haiducek 2009-04-19 22:20:57 UTC 
Please describe the problem:
When saving an event to a CalDAV server, Evolution references the appropriate timezone but fails to include a VTIMEZONE element in the .ics file. This causes problems when other applications (including Mozilla Lightning 0.9) try to read the event from the server.

Steps to reproduce:
1. Connect to a calendar on a CalDAV server
2. Edit an event and save it


Actual results:
Everything looks normal in Evolution, but Lightning 0.9 can't read the calendar.

Expected results:
Evolution should save a VTIMEZONE so that other programs can use the event.

Does this happen every time?
Yes

Other information:
Lightning 1.0pre (current beta version of Lightning) can read the event, but I suspect there are other apps out there with the same problem as Lightning 0.9.
Comment 1 André Klapper 2009-04-20 00:54:13 UTC 
Is this defined somewhere in the RFC?
Comment 2 John Haiducek 2009-05-07 01:37:52 UTC 
Sorry it took so long to reply. Yes, it's in the RFC, section 4.6.5: 'An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object.'
Comment 3 Milan Crha 2009-05-25 21:37:41 UTC 
Thanks for the bug report. I realized and changed myself today, within bug #543069, thus marking as a duplicate. I put it to 2.27 only, as some testing is required before calling it finished. See the other bug report for more details.

*** This bug has been marked as a duplicate of 543069 ***