Well, it's certainly going to be in Fedora 28 which has come out this month. Still delaying the upgrade a bit, we will see..

This issue is not fixed on kde neon.

baloo was using 100+% CPU, and the OS was completely unusable.

Code: Select all

balooctl disable

did not fix the problem either for me, as it did not prevent the baloo_file_extractor from running in the background.

Only after I have done the following, the CPU calmed down:

Code: Select all

rm /usr/bin/*baloo*

Could the deletion now cause any problems with the KDE desktop environment?

This is the OS release I'm using:

Code: Select all

DISTRIB_ID=neon
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="KDE neon User Edition 5.12"
NAME="KDE neon"
VERSION="5.12"
ID=neon
ID_LIKE="ubuntu debian"
PRETTY_NAME="KDE neon User Edition 5.12"
VERSION_ID="16.04"
HOME_URL="http://neon.kde.org/"
SUPPORT_URL="http://neon.kde.org/"
BUG_REPORT_URL="http://bugs.kde.org/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Please don't remove system packages; they will restored at the next update anyway.

You can disable baloo from systemsettings.

tosky wrote:Please don't remove system packages; they will restored at the next update anyway.

You can disable baloo from systemsettings.

I have already tried to disable baloo in the system settings, but it did not prevent the baloo file extractor from running.

These are the setting in the configuration file:

Code: Select all

cat ~/.config/baloofilerc
[Basic Settings]
Indexing-Enabled=false

[General]
dbVersion=2
exclude filters=*.omf,*.nvram,moc_*.cpp,*.m4,CMakeFiles,CMakeTmpQmake,CMakeTmp,libtool,.histfile.*,conftest,.pch,lost+found,*.loT,*.class,core-dumps,CTestTestfile.cmake,*.rcore,lzo,autom4te,.git,*.moc,*.part,*.csproj,*.pyc,confstat,*.gmo,po,*.pc,*.lo,ui_*.h,.hg,confdefs.h,__pycache__,.svn,.moc,CMakeCache.txt,Makefile.am,*.aux,*.po,*.orig,*.o,*.elc,_darcs,*~,.bzr,.uic,.xsession-errors*,config.status,*.vm*,CVS,cmake_install.cmake,.obj,*.tmp,*.swap,litmain.sh,qrc_*.cpp,*.la,*.rej
exclude filters version=2
first run=false

Do I need to set anything else to false, so baloo won't eat away my CPU?

Is there a GUI frontend setup tool to make such changes? Something similar to YaST on openSUSE?

yogi_patrick wrote:This issue is not fixed on kde neon.

This is fixed in Frameworks 5.46. If Neon is not up to date, report a bug there.

I recently did a fresh install of Kubuntu 18.04.
I enabled baloo with content indexing and found that baloo_file_extractor consumed nearly all of my RAM (*GB).
After some experimenting I found the following worked for me:

1) using 'system settings' -> search -> 'file search', disable baloo to clear index file
2) reboot
3) using 'system settings' -> search -> 'file search', enable baloo but DO NOT select 'also index file content'
4) let baloo index your files (I found it to be very quick)
5) using 'system settings' -> search -> 'file search', select 'also index file content'
6) baloo then seems to index file content without consuming many resources.

Obviously in a fresh install steps 1) and 2) are unnecessary.