https://bugs.kde.org/show_bug.cgi?id=493364
--- Comment #1 from [email protected] --- (In reply to pqwoerituytrueiwoq from comment #0) > ... upgrading from kubuntu 22.04 to 24.04 i noticed my DISK/IO LED was never > stopping ... There's a very good chance that Baloo is reindexing everything. There's was a patch to fix issues with BTRFS, sometime over a year back: https://invent.kde.org/frameworks/baloo/-/merge_requests/131 That changed the way they Baloo tracked the files it indexed, unfortunately after the patch Baloo "did just one more index". There's a description in Bug 475919 > ... baloo was set to do everything thing in my home folder both hidden and > content (use case is sometimes i am looking for a config file) ... You might be indexing a *load* of files you don't want to, everything under .cache for example. Have a look at Bug 434705. > It looks appears to be hanging on some files, ones it should not be trying to > index content for, for example mimetype returned application/octet-stream and kmimetypefinder5 returned status code 1 not this was a 12 byte file and it was just sitting on it Not sure here. Did you start with indexing content and then switch to no content? Baloo might have make itself a list of files it needed to index before that change. > i tired turning off content indexing and rebooting, but it will not stop > trying to index content of un-index-able files That also suggests it is working through a backlog of "things to index"... And the fact that baloo_file_extractor appears in "top" > Attempting to load search settings hangs for a while, pausing the serves > takes several minutes, maybe 15? i was not counting, i thought the button was > broken it was so long I don't know on that one. It feels like Baloo is completely overloaded. I would kill Baloo - try a "systemctl --user stop kde-baloo" as that works immediately, then purge the index with "balooctl purge" (maybe "balooctl6 purge"), add in .cache (as per Bug 434705) as exclusions, reboot and let Baloo reindex. It should be a lot better behaved without all the backlog. -- You are receiving this mail because: You are watching all bug changes.
