https://bugs.kde.org/show_bug.cgi?id=457101
--- Comment #8 from gregorystar...@gmail.com --- (In reply to Lemuel Simon from comment #7) > (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. I have a 8 core Ryzen 7 2700x with 16 gigs of RAM. My laptop is running an i5 8350u. Since then, the problem has stopped on my laptop but is still happening every single time on my desktop - I've taken to launching apps via terminal. Could it be my Nvidia GPU (though that wouldn't seem to make sense.) I've tried reactivating baloo and while it no longer wreaks havoc the problem persists. The problem also continues despite removing all KRunner plugins. What sort of system logs would be helpful? -- You are receiving this mail because: You are watching all bug changes.
