Bug 353721 - new events are shifted plus one hour when saving to caldav (horde)
Summary: new events are shifted plus one hour when saving to caldav (horde)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: groupware (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-09 13:35 UTC by Franz Sauerzopf
Modified: 2018-01-31 17:14 UTC (History)
0 users

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 Franz Sauerzopf 2015-10-09 13:35:30 UTC
After creating a new event on a caldav resource (horde 5.1.4) the event displays nicely in Korganizer, Kontact, but is one hour off (later) than the enterd time on the horde calendar. My Korganizer is 4.14.6 on slackware current. Previous Korganizer versions seemed to work alright (not sure).

Did the same test from my Samsung cellphone (android) and from thunderbird from the same computer. Both worked flawlessly. Korganizer reads events from the caldav resource nicely and correct.
 


Reproducible: Always

Steps to Reproduce:
1. add a new event
2. synchronize with horde 5.1.4
3. observe shifted time in horde web-interface or other connected devices

Actual Results:  
The start-time of a new event entered in a caldav calendar (horde) is one hour later than entered in Korganizer/Kontact

Expected Results:  
the same time on both ends

might be timezone related, but I don't know where to check that. Anyway, same test works for a recent thunderbird/lightning calendar (although not in caldav, which does not work with horde).
Comment 1 Franz Sauerzopf 2015-10-19 15:32:48 UTC
I just found ut, this is DST related. Event times are only shifted in summer time, but are transferred correctly in winter (normal) time. I'm central european summer time now.
Comment 2 Denis Kurz 2017-06-23 20:17:34 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:40 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.