https://bugs.kde.org/show_bug.cgi?id=477068
--- Comment #11 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #10) > Maybe when baloo_file does its initial scan through the filestructure to set > up iNotify watches, it could do a sanity check of the folder name against > the DocId. OK, I think that would catch this particular issue. It seems that the FSID change triggers the issue of (comment #3): > Confusing "empty" results when searching from a particular directory (as > opposed to "Your Files"). That's the Bug 474973 but there's no guarantee that this is the only cause. Doing a sanity check of ensuring the folder is indexed before creating an iNotify watch would catch any similar issues. Whatever the root cause. -- You are receiving this mail because: You are watching all bug changes.
