https://bugs.kde.org/show_bug.cgi?id=436737
--- Comment #5 from tagwer...@innerjoin.org ---
Just looking at the original bug - not the crash. If the crash is reproducable
maybe open another bug.
Summary: Sometimes software can be far too clever...
The attachment shows that Dolphin is doing a "filenamesearch". It would
normally do a "baloosearch" however it knows that baloo can be set up just to
index a subset of folders and it knows that if it is not "in" one of those
folders then using baloo doesn't make sense.
You are using Fedora?
Try moving to the Documents folder in Dolphin and searching again. I'm
guessing, with a Ctrl-F, that you'd see a slightly different search dialog, you
had something like:
https://bugsfiles.kde.org/attachment.cgi?id=137170
With baloo running / dolphin in an indexed folder, it should look like:
https://bugsfiles.kde.org/attachment.cgi?id=137169
(Taken from in Bug 435119)
So why might "Fedora" be an issue?
Fedora used to, and I think still does, indexes the Documents, Music, Pictures
and Video folders, not everything under $HOME... You can see this in the System
Settings > Search
You were in "Home" and Dolphin did a filenamesearch scan through all your files
reading each in turn (so, yes, might be slow). Filenamesearch, despite the
name, can also search content however I'm not sure whether it can read PDF's
--
You are receiving this mail because:
You are watching all bug changes.
