When I look into the akondi-configuration GUI I can see in akonadiserver.error that there are many (about 100 lines) of errors:

Code: Select all

Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-92778' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-4391' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-4379' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-4376' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-3962' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" :  "Duplicate entry '563-3954' for key 'PRIMARY' QMYSQL3: Unable to execute statement"
Error during executing ...

This shows up any time I restart the akonadi server or respectively login KDE. Nepomuk, Strigi, file indexing and email indexing are running without any visible problems.

How can I avoid these errors or do they just don't matter? I haven't found any comprehensive information on this error....

thx for reading,
piedro

Did these errors appear out of the blue, or after any change to configuration / accounts?

No, they happen since I am on KDE 4.12. But I cannot tell you about earlier because I had no reason to check.

To make sure it's not my misconfiguration somehow I deleted the ~/.kde4/share/apps/nepomuk files and started from scratch rebuilding the index. It's working on that for over three days now. I use a standard mariadb setup on my local machine and use no options in the akonadi server configuration GUI.

As far I can tell the error log shows this errors (see above) everytime I start akonadiserver

thx for reading,
piedro

THis is still present. 4.12.3

p.

If you have any search folders open, that may be the cause: see https://bugs.kde.org/show_bug.cgi?id=318224 for further information.

You are right! Deleting all search folders solves this problem... and stuff runs faster now ...
that's great ...!

thx , this here is solved as far as I am concerned.
piedro