Baloo file extractor has started working. Whoopee?

I’d gotten so used to seeing baloo_file_extractor crash immediately on
booting - and frequently thereafter - that it came as a shock to me
when, four days ago , I got no warning pop-up after rebooting. However,
since that fateful day, it has been using 98-100% on every one of the 12
processor cores 24/7. This doesn’t seem to have affected performance so
I guess the 14 tags.so processes yield to others where necessary.

Just curious as to how long this might be expected to continue.


Graham Davis, Bracknell, Berks., UK.
openSUSE Tumbleweed; KDE Plasma 5.15.4; Qt 5.12.2; Kernel 5.0.8;
Processor: Intel Core i7-8700; Sound: Intel 200 Series PCH HD Audio;
Video: Intel VGA compatible controller

I kicked baloo and it’s predecessor into the long grass years ago :wink:

If you want a powerful, and very customisable search utility, take a look at recoll https://www.lesbonscomptes.com/recoll/ I’ve been very impressed with it’s performance.

@Cloddy:

What happens when, you use my “clean the Baloo Stygian stables” script?


 > cat bin/KDE_clean_baloo_before_Plasma_start.sh
#!/bin/bash
#
# Clean Baloo …
#
if  -f ~/.local/share/baloo/dateLastCleaned ]]
then
  declare -i BalooLastDate
  BalooLastDate="$(cat ~/.local/share/baloo/dateLastCleaned)"
  declare -i TwoDaysAgo
  TwoDaysAgo="$(date --date='2 days ago' +%Y%m%d)"
  if (( $BalooLastDate < $TwoDaysAgo ))
  then
    /usr/bin/balooctl stop
    /usr/bin/rm ~/.local/share/baloo/dateLastCleaned
    /usr/bin/find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
    /usr/bin/find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
    /usr/bin/date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
  fi
else
  /usr/bin/balooctl stop
  /usr/bin/find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
  /usr/bin/find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
  /usr/bin/date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
fi
#
 >