Filesystem miner can sometimes fail to index a file
It is possible for Tracker's filesystem miner to not index a file that is present in a directory whose contents should be indexed. When this happens, it is not possible to manually index the file with
tracker index -f <file> or
tracker reset -f <file>. The only way to index the file is to use
tracker reset --soft/hard.
I am unsure of what causes this bug, but the next time I run into it, I'll try to post useful information to help debug it.