https://bugs.kde.org/show_bug.cgi?id=510626
--- Comment #5 from skierpage <[email protected]> --- > Have you perhaps disabled baloo, masked its systemd service, or done anything > else non-default vis-a-vis baloo? No. I might have set kf.filemetadata=true and kf.baloo=true in ~/.config/QtProject/qtlogging.ini. > For me baloo doesn't spike, but it does appear in htop. I just updated to Plasma Version: 6.8.2, KDE Frameworks Version: 6.31.0 and running Welcome Center just puts plasma-welcome and baloorunner as top's 2 processes most of the time, with `baloorunner` nowhere near 95-98% of CPU and my load average is only 1.3 - 1.5. So RESOLVED WORKSFORME is fine. > The fact that the mock KRunner actually searches your files is sort of > intended, to showcase the file searching power of KRunner. It is wild once you notice it. Unfortunately I have a bunch of photos named "that time I killed a man in Shanghai...", so the live "time Shanghai" demo is NSFW ;-) -- You are receiving this mail because: You are watching all bug changes.
