https://bugs.kde.org/show_bug.cgi?id=457101
--- Comment #7 from Lemuel Simon <lemuelsimo...@protonmail.com> --- (In reply to gregorystarr00 from comment #3) > (In reply to Lemuel Simon from comment #1) > > Hmm...so far, I can't reproduce the issue. This requires further > > investigation. > > > > There can be many reasons why the search function would behave like that. It > > could be hardware (slow & old HDD) or software (rouge KRunner plugin, > > Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try > > disabling the file search plugins. Also, use a system-monitor like HTop or > > Ksysguard when trying to search again, to get an idea as to which > > application is abusing CPU or I/O. > > I'm running on a M.2 SSd, so I don't think it's hardware speed. I have Baloo > disabled because it was wreaking havoc on my system and using up massive > amounts of ram in the past - is that possibly a cause? Sorry for the late response. Disabling Baloo should render KRunner's file search useless. There has to be another cause. What CPU are using? Also, try disabling KRunner plugins and experiment. -- You are receiving this mail because: You are watching all bug changes.
