https://bugs.kde.org/show_bug.cgi?id=439438
--- Comment #2 from [email protected] --- (In reply to dagobertram from comment #0) > 1. replace the Music folder in your home directory with a link named "Music" > which links to a folder on another HDD > 2. start search in Dolphin with CTRL+F and search for music in your home > directory > 3. search for music after following the link to your "Music" by clicking on > it Ah, ah.... I set up a second disc, added it to /etc/fstab and created a symlink from ~/Pictures to /mnt/disc2/Pictures. Sounds the same setup as yours... Baloo does not follow symbolic links so it does not "naturally" pick up up anything added to the second disc. I created a test file and it was not indexed. However I see that if I go to Dolphin, move down to the Pictures folder and Ctrl-F for a search, I get the search dialog appropriate for a baloo search and no matches (cf attachment). That's not right. Dolphin double guesses what baloo is indexing but "real life" is more complicated. However, I find that if I add ~/Pictures to baloo's "include list", it seems to work. folders[$e]=$HOME/,$HOME/Pictures/ Baloo seems to index the content and it presents the results "under" ~/Pictures. Maybe this is based on "shifting sands" in that baloo relies on a one-to-one match between its internal ID (the device number and inode) and the pathname - and with symbolic links you are creating a potential one-to-many relationships. Could be this leads to further weird, exotic and confusing behaviours 8-] -- You are receiving this mail because: You are watching all bug changes.
