https://bugs.kde.org/show_bug.cgi?id=457335
--- Comment #3 from tagwer...@innerjoin.org --- (In reply to Artur Rudenko from comment #2) > This could be that newly created files remain unindexed > some time after the creation ... Yes, could be that baloo "got stuck". It relies on "iNotify" alerts to see when files are created, deleted or changed - and there are times when baloo misses something. A "balooctl check" brings things back up to date for new or changed files. Purging the index and reindexing is the "start again from scratch" solution. In general though baloo should be quick at noticing new files and changed file details. It knows "content indexing" is harder work and queues up "full text" indexing (something you can watch happening with a "balooctl monitor") > ... Maybe it would be better if dolphin did > fallback to the classic search when baloo can't find needed files? I'm not sure how Dolphin would know that baloo has not indexed particular files. It *does* check what folders baloo is indexing and whether baloo is enabled and "falls back" to it's internal search if it thinks baloo hasn't indexed the folder. That can be messy - Bug 424871, 4th comment shows how messy. -- You are receiving this mail because: You are watching all bug changes.
