https://bugs.kde.org/show_bug.cgi?id=474973
--- Comment #27 from tagwer...@innerjoin.org ---
Maybe I'm a step further. I have a system where I see the same behaviour,
something I consider a remarkable step forward 8-/
Bad news is it's a "bashed about" Neon Unstable, not something I can
reproduceably rebuild. Further bad news is that if I leave the configuration
and test files untouched, do a "balooctl6 purge" and reindex, the behaviour
goes away.
That would help explain why the issue is so slippery. It also means that when
you have the issue, copy your .local/share/baloo/index somewhere safe so you
can go back to it.
It's also quite possible that this is one cause of the problem rather then
"the" cause, but what I see is:
$ baloosearch -i test
144044ed0da2dd /home/test/testfiles/test.txt
14ba610000fc01 /home/test/testfiles
14ba61ed0da2dd /home/test/testfiles
Elapsed: 0.297092 msecs
$ baloosearch -i -d /home/test/testfiles test
14ba610000fc01 /home/test/testfiles
Elapsed: 0.62894 msecs
$ baloosearch -i -d /home/test test
14ba610000fc01 /home/test/testfiles
Elapsed: 0.284228 msecs
$ baloosearch -i -d /home/ test
14ba610000fc01 /home/test/testfiles
Elapsed: 0.278637 msecs
$ balooctl6 purge
$ baloosearch -i test
144044ed0da2dd /home/test/testfiles/test.txt
14ba61ed0da2dd /home/test/testfiles
Elapsed: 0.410179 msecs
$ baloosearch -i -d /home/test/testfiles test
144044ed0da2dd /home/test/testfiles/test.txt
14ba61ed0da2dd /home/test/testfiles
Elapsed: 0.307979 msecs
The index has two records for the /home/test/testfiles folder with different
DocIDs and the "test.txt" file was created with the new format DocID and it was
not found in the search. After the reindex, it was found.
--
You are receiving this mail because:
You are watching all bug changes.
