Akonadi total broken in Kubuntu 10.04.1 LTS

[Juergen Sauer]

Moin,
in current LTS - (!?stable?!)  Release is Akonadi as Backend using Standard MySQL Server in 
Corporate Envirmonets unusable at all.

This Szenario:
1. classic central Server (NIS+NFS), running Ubuntu LTS 10.04.1
2. couple of Kubuntu Desktops around, Classic Setup: User Auth via NIS, $HOME Filesystem served via NFS.

Kmail and Akonadi are currently failing each 2nd login - loosing cmplete all data, for which the Akonadi is the DB Backend was responsible.

Tracing the Problem showed me up, that akonadi for Standard Setups creates an own embedded MySQL InnoDB Database in $HOME/.local and is not able to use Locking or simular techniques to protect those Data against 2nd logins of the same user from an other workstation around. Starting kmail/kontact on an other Workstation destroys all Data off the Akonadi Backend DB. 
The Follow-UP Problem is, that none Kmail/Kontact Instance will start anymore on any workstation.

This Problem hits our Support Lines like a gold rush.

No Solution was offered till now, so we recommend not to use kdepim with akonadi in it, since it is
critical broken.

So, here my Question:

Is it possible to use an remote central PostGresSQL Database instance ?

We tried an akonadiserverrc like this
http://linux.derkeiler.com/Mailing-Lists/KDE/2010-03/msg00173.html

But Akonadi tries sto start it's own PostGresSQL Database instance for it'S own
instead - as expected - to use the offered and perfectly working DB Server on $SERVER.

MySQL is not recomended because of the ownership of Oracle. We want only PostGreSQL!


Is there a Timeline, in the nexrt future to fix those critical Problem in the Kubuntu LTS Repositories ?

J. Sauer

-- 
Jürgen Sauer - automatiX GmbH, +49-4209-4699, juergen.sauer at automatix.de
Das Linux Systemhaus - Service - Support - Server - Lösungen
Geschäftsführer (Managing Director): Jürgen Sauer, 
Gerichtstand: Amtsgericht Walsrode • HRB 120986
Ust-Id: DE191468481 • St.Nr.: 36/201/14198