By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 283 - search field in KDE main menu is slow
Summary: search field in KDE main menu is slow
Status: REOPENED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: i386 Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2010-09-28 02:37 CDT by Denis Prost
Modified: 2018-08-30 03:03 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String: 3.5.12
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Prost 2010-09-28 02:37:36 CDT 
It takes about 10 seconds, on my debian testing system, between the time I enter the string to search and the time it is displayed and results are shown.
Comment 1 Darrell 2012-11-19 15:15:08 CST 
I am unable to replicate this with GIT R14 on Slackware 13.1 32-bit. The response is immediate.
Comment 2 Denis Prost 2012-12-05 07:11:36 CST 
(En réponse au commentaire 1)
> I am unable to replicate this with GIT R14 on Slackware 13.1 32-bit. The
> response is immediate.

I tested it on debian squeeze with 3.5.13.1 : the response is sometimes immediate, sometimes a little slower (2 seconds max) but much better than it was and fast enough from a user point of view, so I set this bug as fixed.

Regards,

Denis
Comment 3 Michele Calgaro 2015-01-28 22:47:07 CST 
I am reopening this bug. I find that on first usage after a reboot or after restarting kicker, the search field is still quite slow, it takes a good 3-4 seconds between the time I type something and the time that something is displayed. Although not a big issue, it would be worth looking into it properly.
This could be caused by another race condition similar to that in bug 1733.