Files lens doesn't search all files

[Nicola Heald]

The files lens only returns results for certain files, and I can't see any pattern to it, here's an example:

    mikeh@bones:~/Documents$ ls screenshot*
    screenshot_saturday_1.png

Search using the files lens for "screenshot" and I get no results. So I figured maybe it doesn't do substring search, but searching for "deen" beings back "GamesdeEntertainment_mp4_5.png", so no idea why one file is included and the other isn't.

[GdH (georgdh)]

I suppose this bug is related to locate part of the scope. When you search for some common string, which can be found more than 128 times in your $HOME (including hidden folders - for example web browser cache could be a big source) and user accessible part of the root directory, you get nothing, if it's not already indexed by Zeitgeist. Reasonable solution could be to build per user databases which would contain only relevant data and use these instead of the global one.

[GdH (georgdh)]

When I said "you get nothing", it should be more like "you get only files from the first 128 entries". When I execute command locate -iec screenshot, I get number 487 but only 27 files are relevant and not all of them are in the list when loocate's output is limited to 128 entries.

[Alex Baggott (alex-baggott)]

I can't recreate this bug on 15.10. Is it fixed now?

[Casey (casey-jao)]

This bug exists on 16.04. On my system, many queries for files in my documents folder return more hits in locate than in the dash, even when the total number of locate results is well under 128.