Summary: | Akonadi can't load resource it created after closing the app (kaddressbook or korganizer) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Alexandre Bonneau <alexandre.bonneau> |
Component: | ICal file resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | critical | ||
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alexandre Bonneau
2013-03-01 00:13:21 UTC
To complete my bug report, here is where and how I got the source files : Vcard files : I copied in a directory all the vcf files from a January backup when I was still using kde 4.9.5 (with that configuration, I couldn't use right click > addressbook properties on my addressbook. Somehow the resource was missing from the "Agents" tab, but kaddressbook worked great anyway). Then I created a vcarddir resource pointing to that directory. Ics files : I copied some files from a January backup when I was still using kde 4.9.5, and used that script (http://paste.ubuntu.com/5576063) to retrieve some events/tasks from a 2nd calendar (which was only into in the Akonadi database). I then imported this ics file into a kcal resource on korganizer 4.9.5, then exported it back into another std.ics file (just to be sure it was generated by korganizer, not by my script). Finally, I created an ical resource on kde 4.10 by importing that std.ics. As said in my previous post, korganizer showed all the tasks/events, but after a reboot, akonadi chocked on that resource. Deleting ~/.local/share/akonadi, ~/.kde/share/apps/akonadi*, ~/.kde/share/config/akonadi* and ~/.config/akonadi, then creating new resources (ical for calendar, vcarddir for contacts) and reimporting the data leads to the same kind of error. The bug isn't specially triggered by restarting korganizer|kadressbook or akonadi as I did so many times before the problem shows up. This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (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. |