Wow, I was searching a long time to find this bug report that I am experiencing. And, surprisingly we've got a very similar setup.

Here:
* korganizer
* ubuntu karmic (9.10)
* amd64
* KDE/Korganizer 4.3.2

1. I start Korganizer (from command line or through an icon)
2. My calendars are loaded
3. I can even open the calendar explicitly through File->Open "mycal.ics"
   if I want - doesn't change anything to the outcome
3. I add some event to the calendar
4. everything is fine
5. I can also press CTRL-S if I want, doesn't change anything to the outcome
6. I quit Korganizer either through closing the window or through File->Quit

There is no error displayed anywhere! Not in the console nor a pop up is shown.

7. I check the file's ctime it hasn't been touched for a week

8. I restart korganizer
9. the added event is gone

In order to make sure, that the ical file was editable I added a few lines with vim to it. Sure enough that worked.

So I removed them again.

And now, after an hour of searching and trying, suddenly, konqueror was able to save the events again.

This sucks. It sucks a lot. I need to be able to rely on korganizer. My brain is a fucking sieve, I need some external medium to manage my appointements and it's not an option to start slipping them because *korganizer* forgot them :-(

OP: What about your korganizer? Does it work by now, 4 months later or not? By the way you may want to vote for the bug.

(In reply to comment #1)


> And now, after an hour of searching and trying, suddenly, konqueror was able
> to save the events again.

Argh... s/konqueror/korganizer/

So, the problem surfaced again here.

While trying to debug it with lsof and cohorts I noticed:

1. when a change some event, then, apparently korganizer will *not* attempt
   to open the relevant cal file and save it there
2. korganizer does not have that cal file open at all

I then additionaly opened the same ressource in korganizer with File->Open and changed the event there.

When I went to the menu and said File->Save korganizer *crashed*:

Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fcbefe08308 in ?? () from /usr/lib/libkorganizerprivate.so.4
#6  0x00007fcbefe05efc in ?? () from /usr/lib/libkorganizerprivate.so.4
#7  0x00007fcbefe0706f in ?? () from /usr/lib/libkorganizerprivate.so.4
#8  0x00007fcbefe070ce in ?? () from /usr/lib/libkorganizerprivate.so.4
#9  0x00007fcbefe499d6 in ?? () from /usr/lib/libkorganizerprivate.so.4
#10 0x00007fcbefe393da in CalendarView::updateView(QDate const&, QDate const&, bool) () from /usr/lib/libkorganizerprivate.so.4
#11 0x00007fcbefe3aec1 in CalendarView::updateView() () from /usr/lib/libkorganizerprivate.so.4
#12 0x00007fcbefe48548 in CalendarView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkorganizerprivate.so.4
#13 0x00007fcbee393ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#14 0x00007fcbf04fb98e in KCal::Calendar::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkcal.so.4
#15 0x00007fcbf05593c0 in KCal::CalendarResources::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkcal.so.4
#16 0x00007fcbee393ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#17 0x00007fcbf0548bef in KCal::ResourceCalendar::resourceChanged(KCal::ResourceCalendar*) () from /usr/lib/libkcal.so.4
#18 0x00007fcbf054a670 in KCal::ResourceLocal::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkcal.so.4
#19 0x00007fcbee393ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#20 0x00007fcbebbf7bc2 in KDirWatch::dirty(QString const&) () from /usr/lib/libkio.so.5
#21 0x00007fcbebbf84a0 in KDirWatch::setDirty(QString const&) () from /usr/lib/libkio.so.5
#22 0x00007fcbebbf8a69 in ?? () from /usr/lib/libkio.so.5
#23 0x00007fcbebbffa31 in ?? () from /usr/lib/libkio.so.5
#24 0x00007fcbebbfff54 in ?? () from /usr/lib/libkio.so.5
#25 0x00007fcbee393ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#26 0x00007fcbee38dd83 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#27 0x00007fcbeec9eefc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#28 0x00007fcbeeca61ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x00007fcbf0c12ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#30 0x00007fcbee37ec2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#31 0x00007fcbee3a9862 in ?? () from /usr/lib/libQtCore.so.4
#32 0x00007fcbee3a725d in ?? () from /usr/lib/libQtCore.so.4
#33 0x00007fcbe7d5ebbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#34 0x00007fcbe7d62588 in ?? () from /lib/libglib-2.0.so.0
#35 0x00007fcbe7d626b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#36 0x00007fcbee3a71a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0x00007fcbeed334be in ?? () from /usr/lib/libQtGui.so.4
#38 0x00007fcbee37d532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#39 0x00007fcbee37d904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#40 0x00007fcbee37fab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#41 0x0000000000408632 in _start ()

I restarted korganizer. Now the same changed entry is *unchanged* in korganizer, however, if I open the ical file again throught File->Open then that identical event *is* changed in the ical file:

  - korganizer default: event unchanged
  - additionaly open the same (?) ressource manually with File-Open:
    event changed

Thus korganizer has become schizophrene.

I note that akonadi is not running.

Could the priority of this bug be raised please? It sucks to loose events in ones calendar.

I think the problem is that korganizer tries to save its stuff into akonadi.

Now, allthough having 2GB of RAM and two cores my computer is slow allready, so I have no interest at all to run additional servers especially not mysql hogging around in my RAM. There will be no akonadi nor mysql here.

I have tried to find a different organizer but have failed so far. Sunbird has a display/layout that is much more clogged than korganizer's which makes it hard to see what's up at a glance. Installing the mega-sw evolution is out of question too. Options? Don't know.

My reason for installing kaddressbook was, that twinkle used it as a phone number source. Since twinkle doesn't support the new way kaddressbook is managing its addresses that reason has evaporated. So now I have all my addresses in kaddressbook and can't really usefully use them any more.

Since KDE 4.4 will have akonadi baked in mandatorily and I am not planning on spending money on a new computer, I'll have to find a replacement for kaddressbook too. It's a pitty.

For now I worked around the problem of korganizer not being able to update my calendar my copying all the fooX.ics files to new foo2X.ics files, removing the old fooX.ics files from korganizer and adding the identical foo2X.ics files. I do hope korganizer will not try to somehow stuff these into akonadi as well and will continue to work. I hope.

The root of this thread is however, that when korganizer is not able to save its stuff it won't say a word to the user and the user will just loose his data. In Debian this would be treated as critical bug and the software would not be released...

Fixed a long time ago.