Summary: | "Find messages..." fails always | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Christopher Heiny <christopherheiny> |
Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | bmarsh, colin.thomson, frederic.coiffier, leo, maurice, peebhat, thomas |
Priority: | NOR | ||
Version: | 4.8.2 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christopher Heiny
2012-05-11 20:10:29 UTC
I also have this problem, using 64-bit Magiea-2 Cauldron, Kmail 4.8.2 Also the 'Stop' button is never available, nor is any search progress info displayed. In adition, occasionally I get the baffling failure: "Cannot get search result. Unknown error. Only resources can modify remote identifiers." The lack of a reliable Find Messages is a potential showstopper for those wanting to use KMail. P.S. I have Local Folders mapped onto a 'maildir' mail directory. I can confirm this error. I searched for a word that is included in some messages. Neither "is not in" not "is in" gave a result. It must have been hard work to get so many bugs in a formerly good software. Seems the Find code is not doing a general 'find search string in To/From field' - as it should - but is checking for a match to the 'pre-@' or 'post-@' component of To/From. But - with either component - it finds only a small subset of what it should find. For example, a Find in 'Sent-mail' for "gmail.com" finds only 11 emails: 5 'this week' 4 in 2004 1 in 2005 1 last week - whereas a Find Messages on the same Sent-mails in KDE 4.5.2 found 395 matches! What concerns me is that there seems no sign of any developer activity with this bug. Is that because (I say hopefully) it is fixed in e.g. KDE 4.9, as is - I heard - the failure to auto-complete email addresses in Composer? Because of this KMail 4.8.* bug I am unable to move from a KDE 4.5.2 environment, as this KMail is unusable because of it. (In reply to comment #4) > What concerns me is that there seems no sign of any developer activity with > this bug. > Is that because (I say hopefully) it is fixed in e.g. KDE 4.9, as is - I > heard - the failure to auto-complete email addresses in Composer? I still see this behaviour in KDE SC 4.9 beta 1. I hope it gets fixed before 4.9 gets released... (In reply to comment #5) > I still see this behaviour in KDE SC 4.9 beta 1. I hope it gets fixed before > 4.9 gets released... Well, yes, but is there no way we can find out whether anyone is actually *doing* anything about the Find Messages mess? I can see that search is finding some results using KDE SC 4.9RC1. It's only showing a limited amount of results, though. I searched for an email with a subject I already knew existed; the email is a few months old and it didn't show up in the search. When I search for something that I know exists and is newer then I can get proper results. In the Maintenance tab of the folder properties I can see that it says the folder was indexed a few days ago. Anyway, glad to see that searching is making progress. Thank you for this and keep up the good work. By the way, this is a duplicate of bug 277007. I confirm this bug. But are the bug-reports reaching anywhere? Yes they are, but to confirm a bug we would need at at least the version you are using, else the confirmation is not useful. Please comment on the master bug, though. *** This bug has been marked as a duplicate of bug 277007 *** Have had this problem ever since switching to kmail2. A thing to note, however, is that when I first switched to kmail2 (11.04?) the migration did not work and I had to mostly migrate manually. Yet I just installed 12.10 beta 1 on another machine (fresh) and search seems to work fine there with kmail2. So I suspect most if not all of the problem is due to a farkled setup of the akonadi/sql/whateverelse files and these might need to be re-created. Why in *(^&% they had to go an complicate a very nice program (kmail) with all the added complexity is beyond me but the users are paying a big price for it. |