292774 – search window, filter window: response time for dialog (popup) window to appear is very slow

Bug 292774 - search window, filter window: response time for dialog (popup) window to appear is very slow

Summary: search window, filter window: response time for dialog (popup) window to appe...

Status:	RESOLVED UNMAINTAINED

Alias:	None

Product:	kmail2
Classification:	Applications
Component:	general (show other bugs)
Version:	1.99.0
Platform:	Ubuntu Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	kdepim bugs

URL:
Keywords:

Depends on:
Blocks:

Reported:	2012-01-29 10:17 UTC by Martin L ü c h e m
Modified:	2017-01-07 22:26 UTC (History)
CC List:	0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Martin L ü c h e m 2012-01-29 10:17:14 UTC

Version:           1.99.0 (using KDE 4.7.4) 
OS:                Linux

It takes between 5 seconds and 60 seconds until the popup windows appears when using extended search or editing filter options. Every change e.g. in the filter dialog takes the same time again.

Last tested with filter dialog:

- to appear: 60 sec!
- seltect different predefined filter: 10 sec

Reproducible: Always

Steps to Reproduce:
use extended search or filter dialog

Actual Results:  
between 5 seconds and 60 seconds until the popup windows appears

Expected Results:  
between 0,25 seconds and 1 seconds until the popup windows appears

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

Comment 1 Denis Kurz 2016-09-24 17:54:51 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 2 Denis Kurz 2017-01-07 22:26:14 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.