Bug 332089

Summary:	Searching on Message Status is unread condition is not recognised
Product:	[Applications] kmail2	Reporter:	Blackpaw <lindsay.mathieson>
Component:	search	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	lindsay.mathieson, me, montel
Priority:	NOR
Version:	Git (master)
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:	http://commits.kde.org/kdepim/4c1deb3db9fff17a60829754b1f98688ec26820d	Version Fixed In:	4.13
Sentry Crash Report:

Description Blackpaw 2014-03-13 10:38:29 UTC

When Searching on "Message Status is unread" I get a:

Search Failed. Errors Found:
  * You forgot to add conditions

Reproducible: Always

Steps to Reproduce:
1. Right click a folder and choose "Find Messages"
2. "Match all of the following"
3. "Message status | is | unread"
4. Click search
Actual Results:  
A rather snazzy looking blue panel expands in the top of the "Find Messages" dialog containing:

Search Failed. Errors Found:
  * You forgot to add conditions

Expected Results:  
A list of unread messages

Comment 1 Laurent Montel 2014-03-13 10:53:45 UTC

I confirm it.
I will investigate today
it's a problem in mailcommon

Comment 2 Laurent Montel 2014-03-13 12:27:10 UTC

Git commit 4c1deb3db9fff17a60829754b1f98688ec26820d by Montel Laurent.
Committed on 13/03/2014 at 12:26.
Pushed by mlaurent into branch 'KDE/4.13'.

Fix Bug 332089 - Searching on Message Status is unread condition is not recognised

FIXED-IN: 4.13

M  +7    -0    mailcommon/search/searchpattern.cpp

http://commits.kde.org/kdepim/4c1deb3db9fff17a60829754b1f98688ec26820d

Comment 3 Blackpaw 2014-03-13 12:45:33 UTC

Confirmed fixed, thanks.

Comment 4 Laurent Montel 2014-03-13 13:24:54 UTC

??? why changed to unconfirmed ??

Comment 5 Jekyll Wu 2014-03-13 13:52:59 UTC

(In reply to comment #4)
> ??? why changed to unconfirmed ??

He/She didn't refresh the page before adding new comment, thus overwriting previous status change.

Comment 6 Blackpaw 2014-03-13 13:55:35 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > ??? why changed to unconfirmed ??
> 
> He/She didn't refresh the page before adding new comment, thus overwriting
> previous status change.

Weird, I opened the page to reply to Laurents fix notification. That should have picked up the confirmed status.

Comment 7 Blackpaw 2014-03-13 13:57:40 UTC

BTW - the blue warning panel no longer shows at all, even if there are no conditions.