[Bug 281227] KMail2 4.7's "Find messages ..." reproducibly fails to search: "Unknown error. (Unable to create persistent search)"

[Ralph Moenchmeyer]

https://bugs.kde.org/show_bug.cgi?id=281227

--- Comment #27 from Ralph Moenchmeyer <rm at anracon.de> ---
(In reply to comment #25)
> It sounds like while some other pretty serious bugs are still there, this
> PARTICULAR bug ("Unknown error" dialog box) is fixed in 4.8 for you, after
> you have deleted and re-added your resources. Can you confirm this?

Back again with the first results. I deleted and re-added my IMAP resource. It
took only some minutes until could access the folder structure, which includes
several GB of mails in a folder structure with about 100 folders. However, the
mail indexer took 150 minutes to index the contents. 

After that the search in a given folder worked for the FROM and TO fields . But
I had to click twice on the search button to get the correct number of hits -
especially when using wild cards in the search term. 

The indexing of mail adresses (better its segments) remains a puzzle to me.
Searching for "TO" adresses that contain "de"  gives less results than a search
for "*.de". A search for TO adresses that contain ".de" (with the dot) gives an
empty result set. From that I would conclude that only segments of the address
are indexed. But even then a search for "de" should give the same amount of
hits as "*.de" - which is not the case. 

OR combinations of search criteria for the TO field do not seem to work at all
- with or without wild cards.  I did not try search conditions with AND
criteria much, but they do not seem to work either.   

In addition, a recursive search through a folder hierarchy does not work. At
least not over three or more levels of the hierarchy. Moreover, sometimes a
search does not work at first. reformulating the search term may give you some
hits. And afterwards suddenly the original search works, too.  

Worst of all - after trying some searches with combined conditions virtuoso-t
suddenly ran amok - using 4 of my CPU cores at a 100% level. This could not be
stopped by deactivating Nepomuk via KDE's system-settings. I had to kill the
virtuso-t process explicitely.  

As an additional test, I am going to stop akonadi, then delete all nepomuk
configuration files and nepomuk directories and start everything again.

-- 
You are receiving this mail because:
You are the assignee for the bug.