Bug 457271

Summary: Baloo indexes files it shouldn't index
Product: [Frameworks and Libraries] frameworks-baloo Reporter: JanLukas <jan>
Component: generalAssignee: baloo-bugs-null
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.92.0   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: File are indexed even though it's disabled in the settings

Description JanLukas 2022-07-29 13:10:20 UTC
Created attachment 150977 [details]
File are indexed even though it's disabled in the settings

STEPS TO REPRODUCE
1. Go to File Search in system settings
2. Set /home/yourname to Not Indexed

OBSERVED RESULT
Index process is shown, and baloo_file/baloo_file_extractor use up a lot of CPU and RAM

EXPECTED RESULT
No files are indexed, and baloo_file/baloo_file_extractor use up little to no CPU and RAM

SOFTWARE/OS VERSIONS
Linux Kernel: 5.15.0-41-generic (64-bit)
Kubuntu: 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Tell me what info else you might need
Comment 1 JanLukas 2022-07-29 13:25:23 UTC
When I disable, purge and enable baloo using balooctrl, it results in this output
> kf.baloo: Failed to add exclude folder config entry for "/home/jan/"
Comment 2 Nate Graham 2022-07-29 17:41:09 UTC
If you don't want it to index your home folder, you should just disable indexing entirely, since your home folder is the only thing it indexes by default. I guess we could add a warning in the UI that you have invalid-ish settings if you add an exclude for your whole home folder, but don't have any includes for sub-folders inside it.

1. Does disabling indexing entirely and then rebooting fix the problem?
2. Can you paste the output of `cat ~/.config/baloofilerc`?
Comment 3 JanLukas 2022-07-29 18:18:30 UTC
1. Disabling indexing, purging and re-enabling it fixed the problem
2.

[Basic Settings]
Indexing-Enabled=true

[General]
dbVersion=2
exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc,moc_*.cpp,qrc_*.cpp,ui_*.h,cmake_install.cmake,CMakeCache.txt,CTestTestfile.cmake,libtool,config.status,confdefs.h,autom4te,conftest,confstat,Makefile.am,*.gcode,*.csproj,*.m4,*.rej,*.gmo,*.pc,*.omf,*.aux,*.tmp,*.po,*.vm*,*.nvram,*.rcore,*.swap,lzo,litmain.sh,*.orig,.histfile.*,.xsession-errors*,*.map,*.so,*.a,*.db,*.qrc,*.ini,*.init,*.img,*.vdi,*.vbox*,vbox.log,*.qcow2,*.vmdk,*.vhd,*.vhdx,*.sql,*.sql.gz,*.ytdl,*.class,*.pyc,*.pyo,*.elc,*.qmlc,*.jsc,*.fastq,*.fq,*.gb,*.fasta,*.fna,*.gbff,*.faa,po,CVS,.svn,.git,_darcs,.bzr,.hg,CMakeFiles,CMakeTmp,CMakeTmpQmake,.moc,.obj,.pch,.uic,.npm,.yarn,.yarn-cache,__pycache__,node_modules,node_packages,nbproject,core-dumps,lost+found
exclude filters version=6
exclude folders[$e]=$HOME/
index hidden folders=true
Comment 4 Nate Graham 2022-07-29 19:26:58 UTC
Ok. Do you seen the same error anymore when you disable, purge and enable baloo using balooctrl?
Comment 5 JanLukas 2022-07-29 19:28:21 UTC
(In reply to Nate Graham from comment #4)
> Ok. Do you seen the same error anymore when you disable, purge and enable
> baloo using balooctrl?

It looks like it's gone, but I will try to replicate the bug again tomorrow when I have some time
Comment 6 Bug Janitor Service 2022-08-13 04:35:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2022-08-28 04:35:57 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!