Bug 409152 - File Search "Do not search in these locations" setting is boolean inverted
Summary: File Search "Do not search in these locations" setting is boolean inverted
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.59.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-24 22:37 UTC by 8192
Modified: 2020-04-19 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of File Search window (40.44 KB, image/png)
2019-06-25 13:29 UTC, 8192
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 8192 2019-06-24 22:37:23 UTC
SUMMARY
In the "File Search — System Settings Module" window (accessible by "File Search" in the Application Launcher has a section captioned "Do not search in these locations".

The drives in this section are, in fact, the ONLY ones in which search works.

If a drive is taken out of this list, implying it WILL work with search, search no longer works for that drive in Dolphin.

If a drive is put in this list, implying it won't work with search, search works with that drive in Dolphin.

This behavior can be easily checked and survives reboots.

STEPS TO REPRODUCE
1. Put a drive in "Do not search in these locations" section of "File Search" window
2. Try searching that drive in Dolphin
3. Take that drive out of the section and repeat 2

OBSERVED RESULT
Drives in "Do not search in these locations" section of "File Search" window are the only ones searchable

EXPECTED RESULT
Drives NOT in "Do not search in these locations" section of "File Search" window should be the only ones searchable

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro 18.0.4
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
None
Comment 1 Nate Graham 2019-06-25 10:33:22 UTC
I cannot reproduce the issue with the same versions as you.

Please attach a screenshot of how the settings window looks for you, and well as the output of the following commands:
- balooctl config list excludeFolders
- balooctl config list includeFolders

Thanks!
Comment 2 8192 2019-06-25 13:29:44 UTC
Created attachment 121129 [details]
Screenshot of File Search window
Comment 3 8192 2019-06-25 13:31:26 UTC
Output of `balooctl config list excludeFolders` is nothing.

Ouput of `balooctl config list includeFolders` is:
/home/8192/
Comment 4 8192 2019-06-25 13:53:52 UTC
If I remove a drive in File Search from the "Do not search in these locations" section, it then appears in the output of `balooctl config list includeFolders`.

However, drives IN the section do not appear in the output of `balooctl config list excludeFolders`.
Comment 5 Nate Graham 2019-06-25 13:55:31 UTC
So what's going on here is that external disks are getting added to the exclusions list by default. To index them, you remove them from that list. Looks to me like this is working, right?
Comment 6 8192 2019-06-25 14:01:49 UTC
For example, take red1. It's in the "Do not search in these locations" list. 

Despite this, search works on it in Dolphin.

It does not appear in the output of `balooctl config list includeFolders`.

I take it out of the list and hit Apply.

Search no longer works on it in Dolphin.

It appears in the output of `balooctl config list includeFolders`.
Comment 7 Nate Graham 2019-07-09 21:45:47 UTC
Very strange, thanks for the info.
Comment 8 Stefan Brüns 2020-03-20 19:46:10 UTC
Please provide the output of

$> balooshow <filepath>

for

1. A file for which search works
2. A file for which search does not work.
Comment 9 Bug Janitor Service 2020-04-04 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2020-04-19 04:33:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!