Version: 3.3.2 (using KDE 3.3.2 Level "a" , SUSE 9.2 UNSUPPORTED) Compiler: gcc version 3.3.4 (pre 3.3.5 20040809) OS: Linux (i686) release 2.6.8-24.11-default it seems to me that korganiser can loose date when a crash occurs. I got confused with some of my appointments because i had to enter them twice (therefore i remember that i have entered it) and they are not stored in korganiser. The crash was definitely not kdes fault (my notebook crashed when i connected a usb-stick/ reader), but there was "enough" time between entering the date and the crash... Maybe the inconsistency comes from the filesystem (reiser, SuSE9.2) and it is not korganisers problem - but in general: when is the entered information written to harddisk? There is no "save" button...
Typically the calendar is saved immediately. However, some resources have some given timeout (e.g. a minute or 10 minutes) to prevent excessive harddisk usage or excessive network traffic. If you'd really save the whole calendar after each small change, that might really slow down the computer (if the calendar file is large enough), since other applications will need to read in the calendar again (like the reminder daemon). Reinhold
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
Saving changes on the calendar is configurable on korganizer in KDE4: you can choose the save policy (after every changes, based on a time interval etc...). I think this report can be reasonably closed.
Yes. I marked "Resolve bug, changing resolution to FIXED". If that is not ok please tell me :-)