Bug 170032 - freeze during typing makes krunner unusable
Summary: freeze during typing makes krunner unusable
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-29 14:26 UTC by Anders Lund
Modified: 2010-01-11 01:20 UTC (History)
4 users (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 Anders Lund 2008-08-29 14:26:36 UTC
Version:           ukendt (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.24-16-generic

After typing 3 letters in krunner, it becomes unusable. It freezes for a while, and does not update correctly. 

I tend to type the word I want, for example 'kontact' and hit return, which appearently opens konqueror.
Comment 1 Dario Andres 2009-01-10 03:01:34 UTC
Can you still reproduce this bug with a recent KDE (4.1.3 / 4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn) ? Thanks :)
Comment 2 Anders Lund 2009-01-10 08:40:38 UTC
Yes, KRunner is still the #1 reason for getting annoyed with kde 4.

The slowness prevents me from opening applications fast, because KRunner insist on not updating the text as I type in it.
Comment 3 Dario Andres 2009-01-10 13:23:44 UTC
What KDE version or revision  are you using?
What is your normal CPU usage? (maybe there is an app taking too much CPU)
You can try disabling some plugins from KRunner (the toolbox icon in the krunner dialog) or leave only the "Applications" and "Command line". Maybe some of the plugins is taking too much time to find possible matches.
Thanks :)
Comment 4 Anders Lund 2009-01-10 18:15:47 UTC
I mostly run KDE 4.1.3. There is no significant CPU usage causing this to happen.
Comment 5 Dario Andres 2009-01-10 18:21:39 UTC
Can you reproduce the freeze when only using the "Command line" plugin (with all the others plugin disabled) ?
Comment 6 Anders Lund 2009-01-10 18:38:22 UTC
Yes.
Comment 7 Stephan Sokolow 2009-02-04 02:16:07 UTC
Same problem here with KDE 4.2.0 though, in my case, it's more a matter of command-oriented KRunner freezing for 1-2 seconds when I type the first letter. (With just the Command Line plugin and nothing else)
Comment 8 Jacopo De Simoi 2010-01-09 12:09:03 UTC
lags/freezes/timeouts should have become less noticeable with 4.3;
with 4.3.4 we fixed a serious bug with respect to pixmap caching which should help a lot when opening/closing the window and in 4.4 this gets even better (provided compositing is enabled).
Can you confirm the reported behaviour with a recent version of kde?
Comment 9 Anders Lund 2010-01-09 12:57:40 UTC
Na, let us close this one, krunner has improved vastly!
Comment 10 Stephan Sokolow 2010-01-09 23:51:38 UTC
Confirmed fixed. I'd have said so sooner, but 4.1 and 4.2 were such a pain that I'd gotten in the habit of using gmrum and xbindkeys.
Comment 11 Xbehave 2010-01-11 01:20:51 UTC
I still have the same/a similar bug in
kde:     4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
qt:      4.6.0
distro:  kubuntu 9.10 (with ppa's not default kde)
arch:    x86_64
gfx-card:radeon (using oss driver) [ATI Technologies Inc RS482 [Radeon Xpress 200M]]
linux:   2.6.32(.0)
xorg:    7.4+3ubuntu10
xorg:    1.6.5+git20091107+server-1.6-branch.2dbcb06a-0ubuntu0sarvatt~karmic

I don't have it quite as badly as Anders (maybe it's a different but related bug), but it will freeze up seemingly at radom making krunner almost unusable. I can consistently trigger it if i type and delete giberish (preferably starting with a program name such as knetworkmanager) for long enough. I was told that the program is less pronounced after longer uptimes but haven't tested that myself.