Bug 209249

Summary: korganizer loses events (Akonadi resource)
Product: [Applications] korganizer Reporter: Janet <bugzilla>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: adam, clara.gnos, finex, janwillem, kde-2011.08, smartins, tpo_deb
Priority: NOR    
Version: 4.3.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Janet 2009-10-02 22:37:13 UTC 
Version:           4.3.1 (using 4.3.1 (KDE 4.3.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-1.slh.1-sidux-686

Very often when I add events to an akonadi ressource in korganizer the event is only shown until korganizer/kontact is closed. After reopening the application the new events are gone and all edited entries are back to former state.
Comment 1 Adam Spragg 2009-10-24 17:52:40 UTC 
I see this also. All new events are lost across a log out/log in. This makes KOrganizer completely unusable for me.

Using KOrganizer 4.3.2 (Debian package korganizer-4:4.3.2-1) on amd64.
Comment 2 Clara Gnos 2009-10-29 16:38:09 UTC 
Bug was also reported at http://bugs.debian.org/553180
Comment 3 Clara Gnos 2009-10-29 16:40:36 UTC 
It seems to work if you use "KDE Calender (traditional)" subresources instead of "ical calender file"
Comment 4 Jan-Willem van de Meent 2010-03-22 11:28:31 UTC 
I just wanted to confirm this behaviour on my system too. I am currently using KDE 4.4.1 on Ubuntu Karmic. My appointments are stored in an ical file.

At times akonadi stops syncing with the ical file. It's not clear to me when this happens. Events are preserved between kontact/korganizer sessions, but can disappear when restarting KDE. After restarting akonadi and korganizer, newly created appointments are written to the ical file again, but events created earlier will still not be synced until modified.

I would suggest increasing the severity rating of this bug. Loss of calendar events is critical in my opinion, since it means the calendaring system can no longer be depended upon for completeness.
Comment 5 Janet 2010-03-24 20:59:34 UTC 
It does work without problems in KDE 4.3.x when you don't use akonadi ressources. No loss of data with plain ical files. But as soon as you use akonadi to store your events data gets lost. I agree that this is very critical, especially as you obviously cannot bypass akonadi in KDE 4.4 as you can in KDE 4.3.
Comment 6 Dotan Cohen 2010-04-11 21:34:11 UTC 
@Janet:
I am using Korganizer in KDE SC 4.4.2 with only the ical and birthday resources, no Akonadi. So you are still safe for KDE 4.4.x
Comment 7 Janet 2010-05-29 16:59:46 UTC 
I'm not sure if this has to do with it or should be reported as new bug:

Meanwhile I'm using KDE SC 4.4.3. My personal calendar is stored in an akonadi-resource. It just happend today I had to move an appointment entry I made yesterday for today two hours into the future. It was sceduled for 1 p.m. so I dragged it to the new position 3 p.m., nothing else changed, the reminder was set to 1 hour before. That was about 10 a.m.

But then, high noon, I got a reminder on the screen: appointment 1 p.m... I looked into korganizer's calendar but only the 3 p.m. entry was there. Don't mind I thought, that akonadi stuff is syncing really slow, forget about it, you'll get another correct reminder at the right time. Guess what? That didn't happen. No reminder at all for the 3 p.m. event, it passed by without further notice until the doorbell rang...
Comment 8 Sergio Martins 2011-07-08 19:06:14 UTC 
The akonadi bridge is no longer used. Korganizer has been ported to akonadi.