Bug 433967

How do you turn off indexing but leave baloo on? Which settings specifically did you change? Can you show a screenshot of your baloo KCM? THanks

Created attachment 136420 [details]
Baloo KCM

I'd check whether baloosearch is finding results for you. See if

    baloosearch yourfilename

works. If it does, go back and have look at your Dolphin search, maybe you are hitting the UI confusion; bug 431240

If you have content indexing turned off and you are searching in Dolphin for a filename, you need to click on the "Filename" button (and maybe also "Your Files")

OK so based on that screenshot, it should be indexing filenames only, not content.

Cannot reproduce, FWIW. I will echo the suggestion to try `baloosearch` and see if that works.

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!

dominich@dominic-80e5:~$ baloosearch adwaitrecolour
Elapsed: 0.449031 msecs
dominich@dominic-80e5:~$ ls ~/Downloads/adwait*
/home/dominich/Downloads/adwaitrecolour

Update: Upon now changing directory to the Downloads folder, I get this:

dominich@dominic-80e5:~/Downloads$ baloosearch adwaitrecolour
/home/dominich/Downloads/adwaitrecolour
/home/dominich/adwaitrecolour
Elapsed: 4.25353 msecs

...and now Dolphin search works, too... weird.

I'm also getting weird behaviour in /, though, despite this:

dominich@dominic-80e5:~/Downloads$ cd /
dominich@dominic-80e5:/$ baloosearch hosts
/home/dominich/Games/sonic-3-angel-island-revisited/drive_c/windows/system32/drivers/etc/hosts
/home/dominich/Games/fortnite/drive_c/windows/system32/drivers/etc/hosts
/home/dominich/Games/epic-games-store/drive_c/windows/system32/drivers/etc/hosts
Elapsed: 1.82707 msecs

dominich@dominic-80e5:/$ ls /etc/host*
/etc/host.conf  /etc/hostname  /etc/hosts  /etc/hosts.allow  /etc/hosts.deny

...and in Dolphin, searching 'hosts' in / produces NOTHING as before.

Some ideas....

... the results in Comment 6 and Comment 7 don't make much sense to me when put side by side

    A plain and simple "baloosearch" doesn't mind where you are when you
    call it, it should give you the same results.
    If you want to filter results by directory, there is a "-d" option.

        baloosearch -d Downloads adwaitrecolour 

    You can try

        balooshow -x ~/adwaitrecolour"

    and

        balooshow -x ~/Downloads/adwaitrecolour

    That will shows you what information baloo has for each file.

    I'm guessing you might have loads of subdirectories and baloo can hit
    a system limit. You can what the limit is with:

        sysctl fs.inotify.max_user_watches 

    If this says 8192 and you've got more than about 8000 folders then
    the indexing will go wrong. You can increase the limit following:

        https://bugs.kde.org/show_bug.cgi?id=433204#c12

    It may also make sense to purge the database and start again "clean"

        balooctl purge

... For Comment 9

    As above, a plain and simple "baloosearch" doesn't mind where you are
    when you call it, it looks up its index. If you

        cd /
        baloosearch hosts

    You'll just get hits just from the folders you've indexed. Assuming
    you've got

        folders[$e]=$HOME/

    in your .config/baloofilerc then you are indexing your home folder
    and below (and if not specified, that's also the default)

    You can experiment with telling baloo to index "/" (without indexing
    file content) but you'll very much need the increase in "max notify
    watches"

... For comment 10

    A search from "/" in Dolphin probably isn't using baloo

    You can search from "/" is dolphin but it walks through the filesystem
    looking for things that match - that can take a while (You'll see a
    "searching" annotation in the bottom right of the dolphin window)

Hope I've got this right - and hope this makes sense!

(In reply to The Feren OS Dev from comment #2)
> Created attachment 136420 [details]
> Baloo KCM
I've revisited this and I've not been able to remove the home directory from the indexing (any more...), maybe it's been fixed so you can no longer shoot yourself in your foot this particular way.

I would say though, your config settings make sense although they might not bring you anything. There nothing wrong, per se, have Baloo running but not currently indexing any folders, it just takes a bit of memory and doesn't do anything.

Dolphin looks at the baloofilerc file to see if it should send the query for a particular folder to Baloo or do a "there and then" search itself. That's a bit of double guessing and maybe it got it wrong.

The behaviour now is if you remove the include entries from ~/.config/baloofilerc, indexing seems to assume $HOME. This is on Neon, Fedora has its own set of hardwired directories (~/Documents, ~/Pictures, ~/Music and ~/Videos).

The other explanations given in Comment 11 still stand I think. Let me know if these cover your problem or we need to do any more troubleshooting.

Setting to "WaitingForInfo" in the meantime, add a comment and reset if you want to keep the issue open.

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!

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.