Bug 292446

Summary:	Stop button never enabled in "Find Messages" dialog
Product:	[Applications] kmail2	Reporter:	Blackpaw <lindsay.mathieson>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	greenrd, lindsay.mathieson, montel, thomas
Priority:	NOR
Version:	1.99.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Blackpaw 2012-01-26 10:06:47 UTC

Version:           1.99.0 (using Devel) 
OS:                Linux

When performing a search, e.g "Subject = *" on my gmail imap account with tens of thousands of messages, the stop button is never enabled, no matter how long the search takes. However the dialog can be just closed.

Reproducible: Always

Steps to Reproduce:
Open the "Find messages" dialog for a large account
Choose a open ended search such as "Subject = *"
Click "Search"

Actual Results:  
Search continues until it is ended or you close the dialiog. Stop button is never enabled

Expected Results:  
Once search starts, Stop button should be enabled, allowing you to stop the search without closing the dialog. This would allow us to change the search parameters.

OS: Linux (x86_64) release 3.0.0-15-generic
Compiler: gcc

Comment 1 Laurent Montel 2012-01-26 11:00:48 UTC

I confirm it .
We can't stop search.

Comment 2 Blackpaw 2012-01-26 11:04:57 UTC

Personally I don't think its a big deal, as its not modal blocking and you can still close the dialog - if its not easily fixed, then just remove the button altogether

Comment 3 Thomas Arend 2012-06-10 10:20:16 UTC

I confirm this bug for 4.8.3

Removing the button is a bad solution. It is a big deal because closing the window does not abort the search. The search continues in the background.

Comment 4 Denis Kurz 2016-09-24 18:24:11 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 5 Denis Kurz 2017-01-07 22:00:39 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.