Comment 4 for bug 1082394

Thank you. The log seems inconspicuous enough so it seems most likely that one of the runners gets stuck so we'll need some additional data.

First please make sure that kde-workspace-dbg is installed.

Make krunner freeze and in a terminal do:

pidof krunner

note the number that spits out, then run

sudo gdb

this will open a debug prompt in which you enter

attach $THE_NUMBER_OF_THE_FIRST_COMMAND

wait a bit until the debugger is done loading (it's done when the prompt re-appears), then run:

thread apply all bt

this will print debug information for all running threads of krunner, you might have to hit return a couple of times to get all data listed. once all data is listed (i.e. prompt is active again) simply copy the output after the command and attach it to this bug report.

##

finally a couple of questions
- Once krunner is frozen, does it start working on its own again? If so, how long does it take approximately?
- Which plugins are loaded in krunner? (can be inspected via the wrench icon left of the input field)
- Does deactivating all plugins except for 'Applications' and 'Command Line' prevent the freezing? (possibly needs a restart to apply)
- When the freeze appears which kded modules are loaded (kcmshell4 kded)? Also please try to stop all services in the bottom list and see if doing so unfreezes krunner again.