Summary: | "Add to Address Book" does not work (akonadi MySQL down?) | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Christoph Lange <langec> |
Component: | addressbook | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | holy, j_kolberg11, roth |
Priority: | NOR | ||
Version: | 1.13.3 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | kdepim 4.6 | |
Sentry Crash Report: |
Description
Christoph Lange
2010-06-21 16:13:34 UTC
I get this too. It wouldn't shock me if this is related to this issue: http://randomguy3.wordpress.com/2010/06/01/d-bus-threading-issues/ But I don't know how to test that. More facts (now from KDE 4.4.5): Sometimes restarting KMail helped. This time it didn't. And the log in ~/.xsession-errors is slightly different: [akonadiserver] Could not contact query service. [akonadiserver] QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! [akonadiserver] Could not contact query service. [akonadiserver] QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! [akonadiserver] Error during executing query "SELECT CollectionTable.id, CollectionTable.remoteId, CollectionTable.name, CollectionTable.parentId, CollectionTable.resourceId, CollectionTable.subscribed, CollectionTable.cachePolicyInherit, CollectionTable.cachePolicyCheckInterval, CollectionTable.cachePolicyCacheTimeout, CollectionTable.cachePolicySyncOnDemand, CollectionTable.cachePolicyLocalParts FROM CollectionTable WHERE ( parentId IS NULL )" : "MySQL server has gone away QMYSQL: Unable to execute query" [akonadiserver] Error during selection of records from table "CollectionTable" filtered by "parentId" = QVariant(, ) "MySQL server has gone away QMYSQL: Unable to execute query" I get that too, with both the address book and with the calendar. The annoying part is that neither kontact nor akonadiconsole complains about this condition. In akonadiconsole, you can see that the entries that were added, but the don't get persisted to mysql and they don't have 'remote id' fields. The only recovery method I have found that works is to 1) stop kontact, 2) restart akonadiserver. 3) start kontact. It makes Akonadi not very useful at the moment. I find myself running akonadiconsole constantly to monitor the condition where it stops communicating with mysql. Couldn’t reproduce this with 4.6 beta5 Fixed in kdepim 4.6 |