I think what you want is the file produced by the "Akonadi self test" dialog box, so here it is.
I confirm that if Akonadi is not running already when kontact starts, then kadressbook displays the "Akonadi is not operational" complaint.
Three remarks:
- Increasing the timeout is just a workaround.
- There is a program with the specific job of making sure that service A is ready when application B starts: it is "upstart" of course. I am not sure about integration with KDE.
- What we really want is that akonadi starts fast.
I think what you want is the file produced by the "Akonadi self test" dialog box, so here it is.
I confirm that if Akonadi is not running already when kontact starts, then kadressbook displays the "Akonadi is not operational" complaint.
Three remarks:
- Increasing the timeout is just a workaround.
- There is a program with the specific job of making sure that service A is ready when application B starts: it is "upstart" of course. I am not sure about integration with KDE.
- What we really want is that akonadi starts fast.
Yours,
Minh