https://bugs.kde.org/show_bug.cgi?id=457335
--- Comment #4 from Artur Rudenko <catcool...@gmail.com> --- (In reply to tagwerk19 from comment #3) > (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. Why does it miss? It's a baloo bug or inotify problem? > > ... 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. Maybe when iNotify notifies about a file created (or modified), baloo should mark parent folder as un-indexed? > 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") But in real situation it is not. For example, try to unpack some archive and then search in unpacked folder. Baloo won't find anything and i think in this case dolphin should just use a general search in this folder (while adding it to index queue), but it doesn't, and it ends up in useless search feature -- You are receiving this mail because: You are watching all bug changes.
