https://bugs.kde.org/show_bug.cgi?id=393059
--- Comment #9 from bugzy <bugzylit...@gmail.com> ---
I was able to find and fix the actual cause of the problem by running the
"calendarjanitor" tool. The tool found an orphaned TODO entry in the affected
calendar. It turns out that whenever I added a new entry into the affected
calendar, the orphaned TODO would cause korganizer to crash when parsing that
calendar. So my new entries (attached above) were not the problem, I was simply
adding new entries to a faulty calendar:
==Output of calendarjanitor (default scan mode):==
Checking for orphans...
[!!]
The following incidences are children of nonexistent parents:
* Found buggy incidence:
id=159344; summary="Set in plant dividers for garden in plot behind
house"
DTSTART=invalid;
DTDUE=invalid;
In fix mode these children will be unparented.
Running the too in fix mode solved the problem and everything has been running
smooth since then.
==Output of calendarjanitor --fix (fix mode):==
Checking for orphans...
[!!]
The following incidences are children of nonexistent parents:
* Found buggy incidence:
id=159344; summary="Set in plant dividers for garden in plot behind
house"
DTSTART=invalid;
DTDUE=invalid;
Children were successfully unparented.
--
You are receiving this mail because:
You are watching all bug changes.
