SUMMARY I've been annoyed by a bug since a very long time. I've finally been able to find the specific case where the search from here is not working! I have an NTFS hard drive that I mount on /mnt/Data. I also have a symlink /mnt/Data -> /home/nathan/Data. I've defined some places in dolphin: Videos ->/home/nathan/Data/Videos, Music->/home/nathan/Data/Music. When baloo is enabled, when accessing those places, the search from here is not working. But if I access those folders by clicking on the external drive then going to those folders, the search from here works even with baloo enabled. I had to edit the places: Videos -> /mnt/Data/Videos and now the search from here is working with baloo enabled. STEPS TO REPRODUCE 1. Create a symlink to a folder 2. Go inside the symlink with dolphin 2. Disable baloo 3. Search from here -> OK 4. Enable baloo 5. Search from here -> KO
I'd say this looks similar to Bug 442786. The interaction between baloo, dolphin and symlinks is particularly messy. Bug 447119 attempts to summarise the various possibilities. The bottom line is baloo does not follow symlinks when indexing and the behaviour when searching (in Dolphin) depends on whether baloo is enabled and what Dolphin thinks(!) baloo has done. (In reply to Nathan Colinet from comment #0) > ... When baloo is enabled, when accessing those places, the search from here is > not working ... If you have followed the symlink in Dolphin and done a search "from", say, /home/nathan/Data/Music and expecting results from /mnt/Data/Music you are stuck. Dolphin thinks that baloo has indexed the folder but baloo has not. I think this is "Case 2" in Bug 447119. > ... But if I access those folders by clicking on the external drive > then going to those folders, the search from here works even with baloo > enabled ... Not sure here: If you have told baloo to index /mnt/Data, then all is OK. If you have not explicitly told baloo to index /mnt/Data, Dolphin will fall back to it's own "there and then" search (irrespective of whether baloo is enabled or not). > STEPS TO REPRODUCE > 1. Create a symlink to a folder > 2. Go inside the symlink with dolphin > 2. Disable baloo > 3. Search from here -> OK > 4. Enable baloo > 5. Search from here -> KO In this case: Where baloo is disabled, Dolphin is doing it's own search. Where baloo is enabled, Dolphin thinks baloo has indexed the folder and it has not (so gets back no results). Call this the first step, it may be that I've misunderstood something. I've tried baloo with NTFS discs and the Paragon ntfs3 drivers and it seems OK, not tried to push the boundaries or use it for "real data" though. https://bugs.kde.org/show_bug.cgi?id=406506#c21 I think flag this as a duplicate of Bug 447119?
*** This bug has been marked as a duplicate of bug 447119 ***