Bug 222870 - iCal/GroupDAV sync problem with EGroupware
Summary: iCal/GroupDAV sync problem with EGroupware
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-15 17:29 UTC by Gunar Schorcht
Modified: 2017-01-07 22:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunar Schorcht 2010-01-15 17:29:50 UTC
Version:           3.4.3 (using KDE 4.3.4)
OS:                Linux
Installed from:    openSUSE RPMs

Everytime when I try to use KOrganizer (working at local timezone CEST) to create a new event in a remote calendar (EGroupware), the event appears to be shifted to UTC in EGroupware and after updating the calendar next time in KOrganizer as well. There seems to be something wrong with timezone handling. The problem happens using iCal and GroupDAV as well. 

I tried to analyse the iCal protocol. What I saw was that the DSTART component for the event is transmitted together with timezone identifier, but the timezone identifier isn't defined in the protocol by a VTIMEZONE component (at least in iCal protocoal). 

EGroupware installation seems to be ok since it works fine with Lightning iCal clients.
Comment 1 Denis Kurz 2016-09-24 18:53:19 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:22:33 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.