Hi,

I'm using KDE 4.7.4 (latest stable version for Gentoo 64 bit). When I try to search for mails using Tools/Find Messages I get an error message from kmail saying

Code: Select all

Can not get search result. Unknown error. (Unable to create persistent search)

At the same time I get the following error message from akonadi:

Code: Select all

Error during executing query "INSERT INTO CollectionTable (remoteId, name, parentId, resourceId, queryString, queryLanguage) VALUES (:0, :1, :2, :3, :4, :5)" :  "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable to execute statement"
Error during insertion into table "CollectionTable" "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable to execute statement"

Any idea what's wrong here? A mail reader that can't search for any mails is near to useless.

Oliver

Search has changed a lot in 4.8, in particular 4.8.1. Does your distro offer the possibility of upgrading?

einar wrote:Search has changed a lot in 4.8, in particular 4.8.1. Does your distro offer the possibility of upgrading?

Yes, but 4.8.1 is currently still unstable in Gentoo. If there's no solution for 4.7.4 I'll have to wait until 4.8.1 becomes stable and use Thunderbird in the mean time for searching.

Oliver

einar wrote:Search has changed a lot in 4.8, in particular 4.8.1. Does your distro offer the possibility of upgrading?

Gentoo has stabilized KDE 4.8.1 today. I upgraded to KDE 4.8.1 and tried to search for a mail using kmail 4.8.1.

I'm getting the same error messages as before (using kmail 4.7.4).

Oliver

Ironically you might want to try 4.8.2 which was out yesterday as there were further improvements in search and mail indexing.

einar wrote:Ironically you might want to try 4.8.2 which was out yesterday as there were further improvements in search and mail indexing.

If searching is generally broken in kmail than it should have been fixed from KDE 4.7.4 to 4.8.1 as I think this is one of the key functionalities of a mail reader. I have more than 4000 mails stored on my system and not being able to search them is critical to me.

If this is not a general bug in kmail then I don't expect it to be fixed if I upgrade to 4.8.2.

At the moment I can't upgrade to 4.8.2 as Gentoo Linux doesn't even add it to its repository yet.

I'll search KDE bugzilla, but if I don't find a solution soon I'll kick kontact and switch to Thunderbird which searches without problems.

Oliver

I don't have 4.8.2 to test (I run git master), but I have seen the commits. Also, I just tested searching myself in my installation, and it worked.

einar wrote:I don't have 4.8.2 to test (I run git master), but I have seen the commits. Also, I just tested searching myself in my installation, and it worked.

So it seems to be a problem on my system. Guess I have to find the reason for this error message:

Code: Select all

Error during executing query "INSERT INTO CollectionTable (remoteId, name, parentId, resourceId, queryString, queryLanguage) VALUES (:0, :1, :2, :3, :4, :5)" :  "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable to execute statement"
Error during insertion into table "CollectionTable" "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable to execute statement"

Unfortunately I'm not an MySQL expert. It looks as if the value ":0" is too long for column "remoteId" in table CollectionTable.

Now, how can I find out the size of this column, is there a way to verify what the correct size should be and can I increase the size? Or can I upgrade or recreate the table so that search will work again?

Oliver

You may want to email the kdepim-users mailing list. Some KDEPIM developers hang out there and will be able to help you.

If you get a solution on the mailing list, please post it back here.

4.8.3 has the same bug.

I have the same problem - kmail 4.8.3

I'm still seeing this with KDE 4.9 beta 2, but I have noticed that I don't actually have a search folder in KMail. Not sure if that is the reason for the errors.

I have the same problem in 4.8.4. Does anyone ask on mailing list or filled bug report?

EDIT: It's broken as hell https://bugs.kde.org/show_bug.cgi?id=277007

A relevant bug seems to be this one: BUG 281227 where comment 11 is the very same problem.