https://bugs.kde.org/show_bug.cgi?id=460460
--- Comment #6 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- (In reply to tagwerk19 from comment #5) > (In reply to Adam Fontenot from comment #4) > > (In reply to tagwerk19 from comment #3) > > ... there are a million Baloo bugs for i/o thrashing, memory > > use, hanging on specific files, incorrect indexing, etc... > OK :-/ > > I'd say though that my experience triaging reports is that the number > reported has settled down *remarkably* over the last two years. Older > versions of baloo that are disappearing as people update their distro's. > Maybe also that I/O load is not so visible with SSD's. Sorry, I didn't mean to be saucy about it. I certainly appreciate the amount of effort that's gone into improving Baloo and understand that it's not easy work. "Millions" was obviously an exaggeration. It's just that Baloo is the one component of KDE in which I encounter show-stopping bugs, over and over again. Other components are at least working well enough that I can "dogfood" and improve them. Baloo I'm forced to keep disabled; once a year or so I give it a try to see if things are better. Judging by user reports on places like the KDE subreddit, I don't think my experience is too far from the norm: https://old.reddit.com/r/kde/search?q=baloo&restrict_sr=on You'll find reports here that are hair-raising to say the least. I do think file name search (Baloo with content indexing disabled) has gotten better; I managed to have it enabled the last few months with not too much trouble... before the combination of Bug 460509 and Bug 437754 forced me to disable it again. -- You are receiving this mail because: You are watching all bug changes.
