[running Kontact 4.3.2 on Kubuntu 9.10]

I'm absolutely desperate to get better control of the calendar in Kontact. I started using it only a few weeks ago. Initially I was using plain *.ics files, and wondering what Akonadi has to do with it all. AND...I could find absolutely NO information about any of this what had any relevance. Distressing. Bewildering.

Then I fumbled through getting Akonadi to ingest my 3 *.ics calendar files, although at this point I'm not entirely sure how.

But I run Kontact on two computers, and use the nifty Unison program to keep them synced. I sync all my *.ics files and the relevant files in /home/{UserAccount}/.kde/share/apps/ and /home/{UserAccount}/.kde/share/config/

But since the great Akonadi ingestion of my *.ics files, things are a mess. I figured out tonight that my *.ics files are still holding my calendar data. But I cannot get computer #2's Kontact to look at more than one of them.

In the Akonadi Resources Configuration section of the Akonadi management tool in System Settings, I have successfully added all three *.ics files as resources. But...it doesn't matter. Kontact ignores all but the first one I added, and I cannot add an Akonadi resource from within Kontact. When I try, from within the calendar, by right clicking on "akonadi resource" or using "add calendar" button (a green cross), I'm told simply "Unable to create subresource {x}"

Can anyone help me out of this mess? If I cannot fix this quickly, I'm abandoning this. I simply have to have a working, transferable calendar.

My recommendation would be to remove the Akonadi calendar in KOrganizer and add three file calendars instead.

KOrganier is not yet capable of using Akonadi directly so it has to go through a kind of wrapper plugin which is OK for most other application's use of calendar data but not KOrganizer's.

Cheers,
_

Thank you very much for information.

Now...why in blazes is this software released with NO documentation saying just what you just told me? It has functionality which is essentially a trap for user. It should be labeled plainly "developmental feature - here's how to use it...but at your own risk". It isn't. That's (choose as many as apply): disingenuous, lazy, plain stupid, destructive of good feeling for the program.

Last night, after some 25 hours of wrestling with Kontact to get various things to work right, I abandoned it. I cannot afford what it's costing me. In four hours, I got Mozilla's Sunbird running and connected to my online public Google calendar, and all my data transfered from Kontact calender to Sunbird. *IT* has considerable online documentation, and, as does Kontact, an active and helpful forum.

I'm sad, because I'd have liked to stay with Kontact. It just cost me too much hassle.

Well, true.

Unfortunately writing documentation is a very time consuming task which we don't have enought volunteers for.
There is an increasing effort to get at least the basics covered at userbase.kde.org with the hope that this will make adding more details noth easier and more rewarding, thus getting more people to help in this area.

However, that being said, the feature of using Akonadi as data source for KOrganizer is not enabled by default. We know that it is more an experiemental feature and thus, have for three releases now, disabled the automated migration/import procedure.

The assumption was that if enabling it requires several hidden and manual steps then those steps will only be attempted by people who want to "test drive" the new architecture as opposed to people who want to do day-to-day work with the respective data.

Especially since it is possible to operate in different data sets, e.g. having normal file resources for the imporant files and using different files as when configuring the Akonadi resources.

Anyway, good to know that it is easy enough to switch to another applications, implying that our choice of storage format can be handled in a non lock-in way (imported or directly used by other applications).

Cheers,
_

Thank for your thoughts. I really enjoyed using Kontact, and thought the interface was especially nice to work with. This database muddle, however, was awful. I just cannot afford the learning curve.

Best of luck with Kontact.