Bug 294568 - Tools=>Find Messages does not seem to work as before
Summary: Tools=>Find Messages does not seem to work as before
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-21 15:43 UTC by Timothy Murphy
Modified: 2017-01-08 06:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Murphy 2012-02-21 15:43:04 UTC
Version:           4.7
OS:                Linux

As I recall, KMail=>Tools=>Find Messages
used to search through the currently opened folder (eg Inbox)

Now it seems to search through all folders,
which in my case means tens of thousands of emails.

Also, it says at the bottom "0 matches in Last Search"
even though it has found dozens of matches.

Also, most of the searches (eg From) do not seem to work properly.

Finally, there are many blank lines is the list of finds.

This facility seems to be in a complete mess,
and has been for many months.



Reproducible: Always

Steps to Reproduce:
Start kmail.
No special or unusual steps

Actual Results:  
As described above, 
KMail=>Tools=>Find Messages does not work properly.

Expected Results:  
Find items in current folder corresponding to choice (Subject, From, etc)
Comment 1 Laurent Montel 2012-02-21 19:54:38 UTC
Update to 4.8.x
Look at if nepomuk works.
Comment 2 Timothy Murphy 2012-02-21 22:19:06 UTC
I don't know what you mean by nepomuk working;
nepomuk_server is running, as well as 7 other nepomuk services
and 3 akonadi_nepomuk services.

Incidentally, if KMail2 depends on Nepomuk working,
wouldn't it be better for KMail2 to check that,
and tell the user if it is not working?

Does KMail=>Tools=>Find Messages work well for you?
Can you search through a single folder?
Does it report "0 matches in Last Search" after the search?
Comment 3 Laurent Montel 2012-02-22 07:21:46 UTC
We inform in 4.8 when nepomuk doesn't work.
In 4.7 no.
Comment 4 Timothy Murphy 2012-02-25 12:23:29 UTC
OK, I've taken the action you suggested, namely to install KDE 4.8. but it did not have the slightest effect on the issue I raised.
(I'm running Fedora-16, and upgraded from Rex Dieter's fedora-kde48.repo.)

So may I ask you in return if you would mind reading my original query, and letting me know, (a) If KMail=>Tools=>Find Messages is meant to work in the way I supposed, and (b) If it does work in this way for you.

To save you time, these were my original queries:
-----------------------------------------
As I recall, KMail=>Tools=>Find Messages
used to search through the currently opened folder (eg Inbox)

Now it seems to search through all folders,
which in my case means tens of thousands of emails.

Also, it says at the bottom "0 matches in Last Search"
even though it has found dozens of matches.

Also, most of the searches (eg From) do not seem to work properly.
-----------------------------------------
Comment 5 Maurice Batey 2012-05-16 10:45:09 UTC
I'm using KDE Kmakl 4.8.2 in 64-bit Mageia-2 Cauldron, and have the same sort of problems as descrtibed earlier in here.

Apart from this Find Messages problem, I am happy with KMail 4.8.2, but until this problem is cleared up then KMail 4.8.2 is UNUSABLE as an email agent...
Comment 6 Maurice Batey 2013-01-20 12:37:36 UTC
No sign of any action since my posting 8 months ago (and since then I have tried KMail 4.9).

Is the problem being addressed, please?
Comment 7 Denis Kurz 2016-09-24 18:22:37 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 8 Denis Kurz 2017-01-07 22:14:08 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.