Summary: | baloosearch doesn't respect --directory parameter | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Saman <svps777+kde> |
Component: | Engine | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | glyphimor, nate, p92 |
Priority: | NOR | ||
Version: | 5.33.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Saman
2017-04-17 17:57:41 UTC
Just confirming this affects me as well. System is gentoo, package is kde-frameworks/baloo-5.34.0. Some quick commands to test: cd ~/tmp mkdir kde-search-test cd kde-search-test mkdir dir1 mkdir dir2 touch dir1/rareword.txt touch dir2/rareword.txt cd .. baloosearch filename:rareword baloosearch filename:rareword --directory kde-search-test/dir1/ (Might have to run "balooctl index kde-search-test/", etc. for the files to get indexed, before running baloosearch.) The baloosearch command simply ignores the --directory parameter. This would perhaps not be too severe if it just affected the baloosearch command; unfortunately, it's also affecting programs tying into baloo. See, for example, bug 379665, 'search is not working in "from here"', filed under dolphin. There, we see basically the same behavior: dolphin returns search results from the entire system, ignoring the "from here" switch that's supposed to restrict results to the current directory. *** Bug 379665 has been marked as a duplicate of this bug. *** Fixed by KF 5.38.0. I confirm it works OK in kubuntu 1710 |