Summary: | Tries to insert existing entries into database | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin Steigerwald <Martin> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | dvratil, kde, piedro.kulman, virgolus |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | xsession-errors.txt with duplicate entry messages |
Description
Martin Steigerwald
2013-04-12 07:23:43 UTC
Created attachment 78834 [details]
xsession-errors.txt with duplicate entry messages
Okay, for whatever reason ~/.xsession-errors is truncated anyway. There is nothing too private in it. So here goes. I excluded lots of basket global shortcut without name error messages from it.
Just for reference, kernel being used is:
martin@merkaba:~> cat /proc/version
Linux version 3.9.0-rc6-tp520+ (martin@merkaba) (gcc version 4.7.2 (Debian 4.7.2-5) ) #5 SMP PREEMPT Tue Apr 9 10:55:51 CEST 2013
(I doubt that it matters)
Is this problem still valid? Can you in Akonadi Console -> DB Console run following query: SELECT collectionTable.name, resourceTable.name FROM collectionTable INNER JOIN resourceTable ON collectionTable.resourceId = resourceTable.id WHERE collectionTable.id = 249; Is pheraps related to databased used by akonady? I've arch as distribution, and mariaDB is used instead of mysql. I should try to use different database? SQLite, for example? Thx for your work guys Ezio, this does not depend on which backend you use (also, SQLite is not really recommended for performance reasons) - this is a bug somewhere in Akonadi/client libraries trying to do something, that we have forbidden to happen. I am getting: ARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323043' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323207' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323405' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323483' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323484' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323485' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-323486' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-324801' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-324939' for key 'PRIMARY' QMYSQL3: Unable to execute statement" Error during executing query "INSERT INTO CollectionPimItemRelation (Collection_id, PimItem_id) VALUES (:0, :1)" : "Duplicate entry '1116-325025' for key 'PRIMARY' QMYSQL3: Unable to execute statement" If in Akonadi Console DB Console I execute: SELECT collectionTable.name, resourceTable.name FROM collectionTable INNER JOIN resourceTable ON collectionTable.resourceId = resourceTable.id WHERE collectionTable.id = 1116; I see: 1 Last Search akonadi_search_resource This is with KDE 4.12 from the Kubuntu KDE backports PPA. Akonadi Console Version 0.99 Using KDE Development Platform 4.12.0 Thanks for the info. It's clear now that we are trying to insert items into a virtual collection that are already there. This does not cause any problems, as you can't have one item linked multiple times into one virtual collection, so if the constraint fails, it means the item is already there and everything's fine. The warning is probably generated from Nepomuk Search code, which does not verify whether the item is already linked. I am not convinced it does nothing. Kmail is working very unreliable and the akonadiserver log shows the above insertion entries. So trying to resolve any issue is a complte nuisance when there are false warnings like this... even if it, as you say, doesn't matter it shows up in an error log and akonadi tells us "found errors in current akonadi start"! How can a user be expected to isolate errors with false positives around? btw: every minor version of kde shows how many kmail bugs have been resolved, but there's a lot of "yeah that doesn't matter" or "works kind of" stuff that get's dusted under the carpet. Creating error messages that need a google search or buglist hunt to find out that they don't matter is a serious bug in my book. And these messages clutter up the error log so it's difficult to find important messages in beetween ... not to mention that it produces these red warning signs when testing the akonadi server via Gui ... plz fix this. thx a lot for your efforts, piedro Forgot to mention: I believe that this slows down the start of Kontact by a huge deal ... it takes minutes on modern hardware to start and be usable... In KDE 4.13 / Akonadi 1.12 we don't use Nepomuk search in Akonadi server anymore, so this problem won't come again. I recommend you update as soon as your distribution ships it. In the meanwhile, you can remove your "Search" folders. thx! the removing of search folders solved the performance issue (I hope)... Just for information: Does this mean there is no searching available anymore? thx for your bughunting! :-) (must be hard work with the complexity Kde has developed...) cheers to progress, piedro (In reply to comment #10) > Just for information: Does this mean there is no searching available > anymore? No, searching will still be available and it will be more powerful than ever (http://news.kde.org/2014/02/24/kdes-next-generation-semantic-search). That is really good news! So let's hope ... (though so often I've been hoping in vain... :-() thx! I don´t see this with Akonadi 1.13 current master with MySQL performance improvements by Dan and Millian, kdepimlibs and kdepim-runtime from 24th of February and KMail 4.14.2 martin@merkaba:~> grep -i "INSERT INTO" .xsession-errors martin@merkaba:~#1> As Nepomuk is not used anymore I am closing this. If someone still has this issue, feel free to reopen or ask me to reopen it in case you can´t do it. |