This file is indeed under the ~/Documents directory. However, when the "From Here (Documents) option was selected, the system didn’t find it, I had to chose “Your files”, then the system found it. Anyone has any clue?
Might be a baloo not having indexed the file kind of thing?
Edit: As a test I created the same file in the same directory and it worked fine for me. Baloo indexing is turned on for me. I know some people don’t use it though.
Doubt it. I don’t have KDE, but I do use Dolphin every day. Search works just fine for me.
It works fine for me too, but I know sometimes people have issues with baloo. For example if they excluded indexing for a certain directory, but not a sub-directory. I don’t believe that works, but some people think it should or just general configuration / indexing issues.
I get that. But Baloo shouldn’t cause Dolphin’s basic file search to have issues.
Then again, this is KDE-related, which is currently in rapid development. So maybe there is a package the OP has that neither of us have that’s causing this. 
I thought baloo was always used unless specifically disabled. That is the only way to fall back to dolphin basic file search?
1 Like
For example, one way for me to know if baloo is being used is that I create a file in an indexed directory. Search for it. It will then find it. If I delete that file and then search for it. It will still show up because baloo hasn’t yet removed it from its index. It takes a bit more time for baloo to catch up.
Yeah, the code for a Dolphin + Baloo setup seems to be off if you need to completely disable Baloo for Dolphin’s basic search to take precedence on a folder you are currently in.
They should tie it to when you click “Your files”, which searches the entire home directory to my knowledge, or make it activate on subfolders only.
Anyway, @apachecai is your system fully up-to-date? And have you used the search feature without issue before?
You could also try this on a different directory and/or files to test things like @d-air1 mentioned.
My system is up-to-date, and this happens to my other two PCs with the same system and setup. Can you advise how I can check if baloo is on or off, and how to turn it on if it’s off. Much appreciated!
@d-air1 All you.
I think it’s essentially using a task manager, like System Monitor or xfce4-taskmanager.
Type "baloo” to check if it’s running.
Also, you can go into KDE System Settings, click on “Search” and locate the system search.
Or just type “baloo” in the search field of KDE System Settings.
In System Settings go down to Search. It should default to file search and check to see if File Indexing is enabled or if you excluded certain folders.
2 Likes
Looks right. If it still doesn’t work you can try to remove your baloo index and let it start over.
I believe you need to do balooctk6 suspend. Then balooctl6 purge. Then balooctl6 resume
1 Like
Purge is enough to rebuild the index, instead of the 3 conmands
2 Likes
I think you sent a screenshot of the wrong thing because Baloo shouldn’t have anything to do with AppImage libraries.
Also, instead of sending a screenshot, please select and copy the output of the terminal, including the command, then post it here as text.
Like @lorebett said, it may be enough to only run:
balooctl6 purge
1 Like
From experience, Dolphin + Baloo can be really finicky on wildcard searches.
For an example ; I have a file called LightningJupiter.jpg - if I search for Lightning, it’ll find it. If I search for Jupiter, or any wildcard element ; eg *Jupiter.jpeg etc, it draws a complete blank.
I’d love for search to be consistent with Dolphin/Baloo, sadly, I haven’t yet found a way to make it work properly.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.