Bug 387941 - "Enable file search" checkbox work at the contrary
Summary: "Enable file search" checkbox work at the contrary
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_baloo (show other bugs)
Version: 5.11.4
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-15 20:30 UTC by mac12
Modified: 2019-11-12 21:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
a video description of the issue (1.41 MB, video/mp4)
2018-01-23 16:17 UTC, mac12
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mac12 2017-12-15 20:30:42 UTC
when "Enable file search" is checked, file search is not avaiable(gives no result instantly),at the contrary when is not checked file search work.
In summary this checkbox works at the contrary.

This is a minor issue but i think its very easy to fix.

Thanks :)
Comment 1 mac12 2018-01-23 16:17:38 UTC
Created attachment 110077 [details]
a video description of the issue
Comment 2 Igor Poboiko 2018-09-27 16:00:38 UTC
My guess is the following: what you disable by this checkbox is the indexer, and not file search itself. Files that are already indexed are still shown.

However, when you re-enable the checkbox, baloo wipes its index entirely and starts building it from scratch. And that leads to no results (immediately after enabling). 

However, after some time they should appear. Is that the case?
Comment 3 Nate Graham 2019-11-12 19:57:54 UTC
Can you answer Igor's question?
Comment 4 mac12 2019-11-12 20:32:28 UTC
(In reply to Nate Graham from comment #3)
> Can you answer Igor's question?

Some time have passed and i forgotten about this issue, i'm very sorry..
Regarding, Igor's question, i don't have issue anymore (reinstalled some weeks ago), now disabling that seems to do no effect (files are still shown), but that is compatible with Igor's description of the issue (assuming that index are not wiped this time).
Comment 5 Nate Graham 2019-11-12 21:39:22 UTC
Thanks! We'll track that with Bug 414077.