Bug 151827

Summary:	korganizer's poor syncronization behaviour causes data lost
Product:	[Applications] korganizer	Reporter:	Olivier Vitrat <ovit.debian>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	lemma
Priority:	NOR	Keywords:	triaged
Version:	SVN trunk (KDE 4)
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Olivier Vitrat 2007-11-03 22:38:49 UTC

Version:            (using KDE KDE 3.5.7)
Installed from:    Debian testing/unstable Packages

Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438979

Using a remote calendar on different machines is extremely dangerous. It
looks like korganizer just overwrites the local calendar when
(re)loading the remote calendar and just overwrites the remote calendar
when saving the local one.

This leads to dangerous situations as happened for me a few minutes ago.
Korganizer failed for some reason to load the changes I've made on a
remote calendar yesterday on startup of korganizer. I made some changes,
not knowing that I was working with an outdated copy of my calendar.
When korganizer finally saved the local changes to the remote calender,
all my changes I've made yesterday on the other machine where gone.

Korganizer should really make sure not to overwrite newer remote or
local calendars when syncronizing. I think it could use the
LAST-MODIFIED fields in the .ics file to check if the local/remote
event/todo-item is newer.

I've decided to use "grave" because it leads to data loss. "Important"
could be appropriate too since "it's not useless for everyone", but I
think data loss weights more in this case.


Cheers,

Bastian

Comment 1 Michael Leupold 2008-09-28 21:03:22 UTC

I can still reproduce this on trunk r865573.

Comment 2 Denis Kurz 2016-09-24 18:47:23 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 3 Denis Kurz 2017-01-07 21:53:15 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.