Version:           embedded 1.0.8 (using KDE KDE 3.2.0)
Installed from:    Debian stable Packages
OS:          Linux

I'm using a prepackaged korganizer-embedded-1.0.8 ipk on a Sharp Zaurus SL-C760 running OpenZaurus 3.3.5 and Opie 1.0.3.  I run it using 'runcompat' which makes gcc2-based apps work in OpenZaurus.

If I run korganizer from a terminal, I see that korganizer loads every appointment in the calendar's 3-year database before the GUI pops up.  Sometimes it fails and seg faults.  If it succeeds, korganizer works fine until exit, when it re-saves the entire database even if no changes were made.  And sometimes it seg faults doing that.

My report is not aimed at the seg-faults, though I can help provide some info there if requested.  I would like to recommend a data-loading model where only the minimal necessary data is loaded up prior to the GUI launching.  Possibly something such as loading up all the repeating events, then the events for the present date, plus and minus 1 month.  Other dates could either be loaded on-demand or in the background.