Why is there a baloo_filemetadat process even though I have disabled baloo?

Question

Why is there a baloo_filemetad process, even though I have disabled baloo?

bruni@bruni-Inspiron-5547:~$ balooctl status
Baloo is currently disabled. To enable, please run balooctl enable
bruni@bruni-Inspiron-5547:~$ ps -A | grep baloo
12863 ?        00:00:00 baloo_filemetad

I am not interested in this purely academically, but this process is often the culprit when something is hanging in my system (I use a lot of mounted filesystems (mainly webdav and samba). I really love KDE since 4.3, but they always seemed to have a thing for file indexing and nonetheless never managed to get it right.

I am on Kubuntu 18.10, KDE Plasma Version 5.13.5.

Answer 1

baloo_filemetadata_temp_extractor ?

If the 'baloo_filemetad' is a truncated version of the 'baloo_filemetadata_temp_extractor':

By Rémi Verschelde in https://bugs.kde.org/show_bug.cgi?id=332065#c32 :

..for metadata extraction to work on non-indexed files in Plasma 5, make sure that you have baloo-widgets installed on your distro (or the package containing /usr/bin/baloo_filemetadata_temp_extractor if named differently). This tool is the one used for on-the-fly extraction of metadata when Baloo's file indexing is off.

$ baloo_filemetadata_temp_extractor
Usage: baloo_filemetadata_temp_extractor url

Arguments:
  url

---Edit---

It seems that the 'ps -A' will truncate the output

With the:

$ watch -n 1 'ps -A | grep baloo'

With the KDE System Activity: