[Korganizer-devel] [Bug 151827] New: korganizer's poor syncronization behaviour causes data lost

[Olivier Vitrat]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151827         
           Summary: korganizer's poor syncronization behaviour causes data
                    lost
           Product: korganizer
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: korganizer-devel kde org
        ReportedBy: ovit.debian gmail com


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