https://bugs.kde.org/show_bug.cgi?id=333655
Barney Holmes <djbar...@djbarney.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djbar...@djbarney.org
--- Comment #65 from Barney Holmes <djbar...@djbarney.org> ---
It should not be aggressive it should be NICE. Talking of which it has the
lowest NICE priority and yet uses 100% of CPU, surely something is wrong there
? But I'm no expert on nice. I had to use "cpulimit" to throttle the process
which helped a bit but still get really annoying GUI freezes. Can someone fix
this please ? To me its a major KDE bug that can ruin the experience for new
users not aware of the indexer and should either be turned OFF by default or
removed. I actually still have it running because I'm curious to see if it does
eventually provided useful search function on my 51GB of user docs and graphics
files and so forth.
Until then the root of this problem may be in the philosophy of the developers
...
"There is no explicit “Enable/Disable” button any more. We would like to
promote the use of searching and feel that Baloo should never get in the users
way."
http://vhanda.in/blog/2014/04/desktop-search-configuration/
What does "promote the use of searching" mean ? It's up to the user and only
the user what they want or need to use not some "promotion" thing. Also "should
never get in the users way" ... well it does, and really badly as well, this
problem goes back to 2014 and has still not been fixed. What is going on here ?
--
You are receiving this mail because:
You are watching all bug changes.
