Trying to cleanup my akonadi database lead to this, which is not reproducible: "vacuuming database, that'll take some time and require a lot of temporary disk space..." "optimizing table SchemaVersionTable..." "optimizing table ResourceTable..." "optimizing table CollectionTable..." "optimizing table MimeTypeTable..." "optimizing table PimItemTable..." "optimizing table FlagTable..." "optimizing table PartTable..." Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" : "Duplicate entry '59-cdash' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" Error during insertion into table "CollectionTable" "Duplicate entry '59-cdash' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" "optimizing table CollectionAttributeTable..." Error during executing query "UPDATE CollectionAttributeTable SET collectionId = :0, type = :1, value = :2 WHERE ( id = :3 )" : "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" Error during updating record with id 421 in table "CollectionAttributeTable" "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" "optimizing table PimItemFlagRelation..." "optimizing table CollectionMimeTypeRelation..." "optimizing table CollectionPimItemRelation..." "vacuum done" Reproducible: Couldn't Reproduce
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.