2 May
2014
2 May
'14
22:15
On Friday 02 of May 2014 17:56:36 C wrote:
I could try clearing the Baloo database file. I'm guessing that would trigger Baloo to re-index? Will that work to reset things and put Baloo back to initial status to see if the CPU load and I/O is still happening? i guess it's up to you =) but, if you want start again, stop any baloo client (e.g. dolphin, gwenview, akonadi), baloo_file itself, remove contents of ~/.local/share/baloo, and remove the first run=false key from ~/.kde4/share/config/baloofilerc and proceed as usual...
Cheers, Hrvoje
C.