Bug 267031

Summary: events entered in kontact move an hour earlier when read from egroupware calendar
Product: [Applications] korganizer Reporter: George Avrunin <avrunin>
Component: groupwareAssignee: kdepim bugs <pim-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: cannewilson
Priority: NOR    
Version First Reported In: 4.4.10   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description George Avrunin 2011-02-24 02:12:21 UTC 
Version:           4.4.10 (using KDE 4.5.5) 
OS:                Linux

I use kontact/korganizer with an egroupware calendar maintained by my department through the groupdav connection.  If I enter events in egroupware, they show up correctly in kontact.  If I enter an event in kontact, it initially shows at the correct time, but as soon as the calendar is reloaded, the event moves to a time one hour earlier.  Both machines are in the North America/New York time zone and have the system clock on UTC.  This occurs with both egroupware 1.6 and 1.8 (both community edition).  If I access the egroupware calendar with sunbird through groupdav, this problem does not arise.  

Reproducible: Always

Steps to Reproduce:
1. egroupware calendar on server
2. Add calendar in kontact with groupdav (http://example.com/egroupware/groupdav.php)
3. enter an event at some time, say 2:00 pm in kontact for the egroupware calendar


Actual Results:  
After calendar reloads, event moves to 1 hour earlier (1:00 pm if entered for 2:00 pm)  When the calendar is viewed in egroupware, event is at 1:00 pm.

Expected Results:  
Event should show at 2:00 pm in kontact and egroupware
Comment 1 Denis Kurz 2016-09-24 18:42:12 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 21:53:43 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.