You can restrict it to whatever you want in system settings.
As a side note, you stated you want to keep using it and you also stated you followed @Kresimir’s instructions and ran balooctl disable. If you want to keep using it, you probably shouldn’t disable it.
Oh, for that, pdfgrep works like a charm.
Just to update you.
Restarted the machine and found
[limo@lenovo ~]$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexing: /home/limo/LimoData/Zim/ZIMBooks/The General Theory of Employment Interest and Money John Maynard Keynes.pdf
Total files indexed: 156,983
Files waiting for content indexing: 20,777
Files failed to index: 0
Current size of index is 2.56 GiB
[limo@lenovo ~]$
Definitely I didn’t 
add all these in no time.
Then you haven’t disabled it.
This is what I get:
~🐸 balooctl status
Baloo is currently disabled. To enable, please run balooctl enable
What do you want, have Baloo enabled and use it, or disable it and not use it?
This was over the past 2 days when I was trying to find out where the problem comes from.
I think thes are the main two things I should try to do now.
Let me go to “System Settings” and see 
If you are not using KDE Plasma, but Baloo+Dolphin on Xfce (as you’ve said in some other thread… why would you do that? I have no idea, but okay…), then you won’t have the same System Settings tool that @dalto is referring to.
I tried several DE, currently after installed default offline XFCE, then LXQT, then KDE Plasma (removing previous DE of course).
I wish there is a KDE Plasma ISO.
Why? Are you for some reason unable to do an online install?
Per default baloo only indexes your home directory and excludes any hidden files and folders. On top of that there’s an extended exclude list of items which should not be indexed (like binary files).
I suggest to run
balooctl disable; sleep 5; balooctl purge; sleep 5; balooctl enable;
which resets the baloo index. Then let baloo run the indexing (observe via balooctl monitor if you want) until it is finished. Once the index settles there shouldn’t be any noticeable baloo activity (at least on an SSD), except for a) a lot of file changes or b) reindexing after an update.
If you notice a slowdown check with balooctl monitor what’s going on.
Depending on your system you may want to manually exclude folders (see Settings → “File Search”). If you’re certain you’ll never search folders with baloo and there are many files in them exclude those folders. A prominent example is source code if you’re a programmer. Or if you have directory with ebooks you probably don’t want to search those on a word basis with baloo. Along those lines.
Yes, I tried several times to get connected but no way. It didnt work. I almost tried everything I found to connect.
OK. I don’t mind. I already checked system settings, and found it only working on my home folder.
But I think I should first
exclude TimeShift as @dalto mentioned.
I don’t know how t do both things @dalto mentioned above. Sorry.
Baloo shouldn’t index anything in /run. If in doubt you can always use balooshow -x <path> to check if baloo indexed an item and what it knows about it.
I did:
[limo@lenovo ~]$ balooshow -x /run/timeshift
/run/timeshift: Not a valid url or document id
[limo@lenovo ~]$ balooshow -x /home/
The document IDs of the Baloo DB and the filesystem are different:
Url: /home/
ID: 1099511627801 (DB) <-> 1099511627838 (FS)
Inode: 256 (DB) == 256 (FS)
DeviceID: 25 (DB) <-> 62 (FS)
1000000003e 62 256 /home/: No index information found
[limo@lenovo ~]$
How to exclude TimeShift?
I assume it is so, but @dalto mentioned in above post to exclude time shift, I don’t know exactly how to do it.
I don’t want to execute the commands you gave and find myself in same situation.
Can you please tell me how to exclude time shift? (from indexing? from search? from Dolphin?.. from…?)
Does this indicate something?
I don’t know what’s going on there, but that doesn’t seem right. Here:
❯ balooshow -x ~
10100000029 41 257 /home/schlaefer
Mtime: 1632415853 2021-09-23T18:50:53
Ctime: 1632415853 2021-09-23T18:50:53
Internal Info
Terms: Mdirectory Minode T9
File Name Terms: Fschlaefer
XAttr Terms:
~
❯ balooshow -x /run
100000017 23 1 /run: No index information found
When it said “no index information” for me I thought because I disabled baloo…
A bug perhaps?
Should I try what you suggested:
What about it forgetting and reindexing? what about search returning multiple results?
What you think?
If you are only indexing /home, then /run/timeshift shouldn’t need to be excluded.