Search *.epub = no items found CLI: find -name *.epub | wc -l = 225
There isn't enough information in this bug report to be actionable. At the minimum, we need the following additional pieces of information: - Dolphin version - KDE Frameworks version - Is Baloo active? - If so, does `baloosearch *.epub | wc -l` show about 225 results?
If you can provide the information requested in comment #1, please add it.
Created attachment 108031 [details] attachment-29187-0.html I have no idea how to get the version number of dolphin, did not include that in the menu (like most programs) Have no idea how to get the KDE frameworks version, again the software does not provide a like to that information of it's hidden well.what is baloo... something from the jungle book?find works = 226baloosearch = 1 On Tuesday, September 5, 2017 3:11 PM, Nate Graham <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=384391 Nate Graham <pointedstick@zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pointedstick@zoho.com Resolution|--- |WAITINGFORINFO Summary|does not work |Searching in Dolphin does | |not work Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Nate Graham <pointedstick@zoho.com> --- There isn't enough information in this bug report to be actionable. At the minimum, we need the following additional pieces of information: - Dolphin version - KDE Frameworks version - Is Baloo active? - If so, does `baloosearch *.epub | wc -l` show about 225 results?
You can get Dolphin's version number in one of two ways (depending on whether you have the main manu bar hidden or not) 1. Help menu > About Dolphin [it shows the version number] 2. Control button on the toolbar > Help > About Dolphin [it shows the version number] You can find the KDE Frameworks version in the Info Center program. That said, it's now clear that this isn't Dolphin's fault, it's Baloo's (reassigning there). Baloo is the search framework. I'm sorry to hear that it's not working for you. This is a pretty common problem, and we know it's got some bugs. What does `balooctl status` say? In the meantime, as a workaround, try disabling it and re-enabling it: `balooctl disable && balooctl enable`
My problem was that Baloo did not find files more than about a year old. Disabling and Enabling cured it.
Created attachment 108083 [details] image.png On Thursday, September 28, 2017 8:55 AM, "bugzilla_noreply@kde.org" <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=384391 tshunter001@yahoo.com.mx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tshunter001@yahoo.com.mx --- Comment #5 from tshunter001@yahoo.com.mx --- My problem was that Baloo did not find files more than about a year old. Disabling and Enabling cured it.
Created attachment 108084 [details] image.png