Bug 231774 - Krunner hangs on backspace
Summary: Krunner hangs on backspace
Status: RESOLVED DUPLICATE of bug 203668
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-22 14:35 UTC by Cody
Modified: 2011-12-08 17:51 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Cody 2010-03-22 14:35:54 UTC 
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Fedora RPMs

Note: Krunner does not crash in this instance.

Launch krunner (alt+f2) and enter the word 'top'

Now backspace one character and krunner will halt/freeze up to 45 seconds. I have confirmed this behavior in 4.4.1 with multiple people in #kde.

Thanks
Comment 1 Cody 2010-03-22 18:42:13 UTC 
Ok, I have found for information on this.

This bug is being caused by the "Control Audio Player" plugin + Amarok running. 

If you disable the plugin the backspace freeze/hangup stops completely.

or

You can simple ensure amarok is not running and the freeze will disappear during a backspace.


The following link may be of help or related.

http://mail.kde.org/pipermail/amarok-devel/2010-March/006799.html
Comment 2 Nico Schlömer 2010-05-16 11:51:33 UTC 
I can totally confirm the bug and the work-around.

After having typed just about anything, backspace will freeze the UI for about 20 or so seconds.

-- For KDE 4.4.3 that is, btw!
Comment 3 Elián Hanisch 2010-06-15 16:38:59 UTC 
duplicate of https://bugs.kde.org/show_bug.cgi?id=203668
please comment on that bug if you still see this problem on 4.4.2 or later so it can be reopened.
Comment 4 Georges Dubus 2010-06-15 18:34:49 UTC 
Looks like it's solved on 4.4.2. Thanks !
Comment 5 Jekyll Wu 2011-12-08 17:51:03 UTC 

*** This bug has been marked as a duplicate of bug 203668 ***