Summary: | Akonadi Resources and KOrganizer Calendar Resources not in Sync | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Andreas Cord-Landwehr <cordlandwehr> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | major | ||
Priority: | NOR | ||
Version: | 0.9 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Andreas Cord-Landwehr
2011-12-24 09:07:01 UTC
I am still not sure how the resource got broken, but at least I can say why deleting these broken resources at KOrganizer does not work: In file kdepim/korganizer/akonadicollectionview.cpp at line 506 (referring to current GIT) there is the following snippet that calls deletion: if ( instance.isValid() ) { Akonadi::AgentManager::self()->removeInstance( instance ); } But for the broken resources the call of instance.isValid() returns false. The reason is, that my broken resources, i.e., the "instance" object contains an empty string at instance->mIdentifier. Checking the presence of an identifier name is the validity check here. Hence somehow this string must got lost. Unfortunately, I still could not find a way yet to reproduce this problem. At least I found a way to resurrect the resources(and then to be able to delete them afterwards) == workaround. To resurrect the resources I had to modify the file "~/.config/akonadi/agentsrc" and add a corresponding line at the block "[Instances]" for the resources without agents. Apparently, all the corresponding files in * .kde/share/apps/akonadi-davgroupware/ * .config/akonadi/ * .kde/share/config/ for the resources still exist. It looks for me like the deletion of the agent broke somewhere after removing this config line. After adding the corresponding line and restarting Akonadi the agents reappeared at the Agents-List of Akonadi-Console. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |