As the title says, the bug is probably behind these widgets, as a search in Krunner , too, does this. However, the bug is not reproducible on every search. Sometimes, things go fine, sometimes the CPU usage spikes and then stays at that level. I filed this bug under plasmashell and not under baloo because KSysguard points to plasmashell/krunner (whichever is used for search) as the culprit, while baloo's footprint is as low as it can be. Steps to reproduce (not always reproducible): 1. Open Launcher Menu or KRunner. 2. Type in a search query. 3. The query works smoothly, the result opens great. But the CPU usage of plasmashell/krunner goes within the described range, and stays there untill the process is killed off and respawned. Things go back to normal thereafter. One thing to note is that this didn't happen till I upgraded the Plasma packages to 5.9.4 last night. In other words, 5.9.earlier-version was probably working good, though I have nothing to back that claim.
Same bug here. Fedora 25 with KDE
Hey there, I am have an exactly same bug here.
Encountered this too. It seems that the plasmashell process jumps by 25% increments representing 1 of my 4 cores on the CPU. Navigating the kicker does not trigger this, only search. Search also works fine in other sections of KDE. I'm also using Fedora 25 with plasma 5.9.4-1
The disabling of "file search" solved the problem... The problem seems to be there. I am using F25 with plasma 5.9.4
Having filed the bug, I feel responsible to post a (perhaps positive) update. The problem persisted for few days after filing the bug; to the point I ended up not using the file search via KRunner/Launcher - the most valuable DE function besides window switching from my POV. However, since 2 days, the problem seems to have gone. I hammered Krunner and Launcher with random search queries, but they didn't rile up. Unfortunately, I haven't kept track of the Fedora system updates since the day I filed the bug. May be others can chime in with better inputs.
At this point I guess this bug was fedora specific. If you've been updating you may have seen it survive a plasma package update, but after that sometime last week a "plasma-settings" package dropped, I assume this is fedora's settings for plasma. I haven't seen the bug since, but I've been avoiding triggering it.
(In reply to Travis J from comment #6) > At this point I guess this bug was fedora specific. I agree with you; so far only Fedora users have reported this bug. > If you've been updating > you may have seen it survive a plasma package update, but after that > sometime last week a "plasma-settings" package dropped, I assume this is > fedora's settings for plasma. I do recall seeing plasma related package(s) in one of the updates, but felt it was too ambiguous to mention here. > I haven't seen the bug since, but I've been > avoiding triggering it. I suggest you to try. I hope the other participants do the same; it would free Kai Uwe as soon as possible from this bug.
Alright, I am not longer able to trigger this. Also, I looked in the redhat bugzilla for fedora and found the bug ticket on their side. It had to do with baloo zombie child in krunner or the like. And yes it has been makred resolved with the kde-settings package. I believe you can close this issue now. https://bugzilla.redhat.com/show_bug.cgi?id=1432619
Thanks for the update; closing.