Bug 169414 - Korganizer corrupts tasks hierarchy
Summary: Korganizer corrupts tasks hierarchy
Status: RESOLVED DUPLICATE of bug 112508
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-19 00:33 UTC by Arturo Hoffstadt Urrutia
Modified: 2009-03-08 21:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arturo Hoffstadt Urrutia 2008-08-19 00:33:41 UTC
Version:           4.1.0 (using 4.1.00 (KDE 4.1.0), 4.1.0-5.fc10 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.11-97.fc9.i686

2 loaded plugins (print style, anual and diary).

No backtraces, since it just corrupts parts of the hierarchy, and then, functions normally.

It seems to affect trees with more than 2 levels.
I tried to reproduce it, but failed trying. My file is a big one (12-14 Tasks, with 4 or 5 level subtaks)

When I close Korganizer (and korgac), and open it again, only a 2 level task tree is available. It simple picks all de tasks that are in the level before the last level, and put it as a first level tasks.

Expected Behaviour is that the hierarchy is conserved from restart to restart of Korganizer (and korgac).
Comment 1 Reinhold Kainhofer 2009-02-17 13:00:43 UTC
I can confirm this. The problem appears to be that KOrganizer stores the hierarchy using the UID of the parent as well as a pointer to the parent incidence in memory (which is set when loading the calendar). Now, if the parent event is not available when loading (or maybe even some bug crept in that depends on the order of the tasks being loaded), there is no pointer to the parent and the UID of the relatedTo() setting is apparently reset and cleared...
Comment 2 Thomas McGuire 2009-03-08 21:10:31 UTC

*** This bug has been marked as a duplicate of bug 112508 ***