Bug 332435 - search window says "7 matches" but shows 13 mails
Summary: search window says "7 matches" but shows 13 mails
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: search (show other bugs)
Version: 4.13 Pre
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-22 09:26 UTC by Martin Koller
Modified: 2017-01-07 22:15 UTC (History)
1 user (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 Martin Koller 2014-03-22 09:26:13 UTC
Using the new Baloo engine is great. However in the search window when I search e.g. "To" for "someName" in all folders (I have mails only in maildir), it tells the "7 matches" but in fact the list shows 13 mails (In general: it often show more mails in the list than what the number of matches tells).
Checking the list reveals that some mails show twice, where in fact inside the folder the mail really only exists once.
Interesting is, when I click a second time on the "Search" button inside the still open search window, then the list is reduced and now only shows the number of matched mails (but now the number of matches at the left bottom is replaced with "Search complete."  - which seems to be probably a different bug as it always should tell me the number of matches)

Reproducible: Always
Comment 1 Andrew Gaydenko 2014-04-19 12:42:33 UTC
Confirming. I have met situations when search result contains dozens duplicates of the same message.
Comment 2 Denis Kurz 2016-09-24 18:15:49 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 3 Denis Kurz 2017-01-07 22:15:51 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.