Bug 429910

Apparently the “Delete entry” button has been disabled in the meantime, but that is only a facade. Changing to “Not indexed” still pollutes the configuration with contradicting items instead of changing the configuration.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3

(In reply to David Hurka from comment #1)
> ... Changing to “Not indexed” still pollutes the configuration
> with contradicting items instead of changing the configuration ...
Oh yes, I have seen it happen. Now, can I get it to do it again?

(In reply to tagwerk19 from comment #2)
> ... Now, can I get it to do it again?
Most straightwordly, if you have a .config/baloofilerc containing:

    [Basic Settings]
    Indexing-Enabled=true

    [General]
    dbVersion=2
    exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc... et al...
    exclude filters version=8
    exclude folders[$e]=$HOME/

Gives you the two lines in the System Settings -> Search, one with "Indexed" and one "Not indexed"

Irremovable item of `/home/<username>` with the `indexed` value persists.

---
System Info:

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.0-1-MANJARO (64-bit)
Graphics Platform: X11

```
$ pacman -Qi krunner 
Name            : krunner
Version         : 5.85.0-1
...
```

(In reply to pveax from comment #4)
> Irremovable item of `/home/<username>` with the `indexed` value persists.
What do you have in your .config/baloofilerc file?

Specifically, the "folders[$e]" and "exclude folders[$e]" lines. You might have ended up with something like

    folders[$e]=$HOME/,$HOME/

or the config referred to in Comment 3

> What do you have in your .config/baloofilerc file?

Hi, tagwerk19!

Currently it is:

```
[Basic Settings]
Indexing-Enabled=false

[General]
dbVersion=2
exclude filters=<long line. hidden 'til the end of line>
exclude filters version=8
only basic indexing=true
```

But I have that /home/<username> item in the `Folder specific configuration:` list.

Most probably it is hard-coded somewhere.
The issue `Reported:	2020-12-01`.
Is it almost impossible to that bug to be that complicated to locate it in code and to understand why it was hard-coded instead of using configuration which contains the `~/.config/baloofilerc` file.

Probably the bug is poor-described. Let me fix it:

Behavior is the next:
0. Press "Start" btn (meta key)
1. Open `System Settings`.
2. Go to `Workspace` section. Than `Search` -> `File search`.
3. Check `Enable File Search` to enable it.
The `Folder specific configuration:` became editable. It contains /home/<username> item with the `indexed` option chosen by default. it is the only item in the list.
4. Press `Apply`.
5. Switch to `KRunner` item in the left panel (there are 3 items only, 3rd is `Web Search Keywords`).
6. Switch back to `File Search` item.

Only 1 item is present. No changes.

the `~/.config/baloofilerc` file became:
```
[General]
dbVersion=2
exclude filters=<hidden>
exclude filters version=8
only basic indexing=true
```

7. We have only one item listed. Change it mode from `Indexed` to `Not indexed`.
8. Hit `Apply` btn.

No I see the the only item in that list.
The `~/.config/baloofilerc` file became:
```
[General]
dbVersion=2
exclude filters=<hidden>
exclude filters version=8
exclude folders[$e]=$HOME/
only basic indexing=true
```

9. Re-do the (5) and (6) steps (so just switch to show another component settings and back).
10. Now I see that 2 items are listed:
/home/<username> Indexed
/home/<username> Not indexed

The `~/.config/baloofilerc` file became:
```
[General]
dbVersion=2
exclude filters=<hidden>
exclude filters version=8
exclude folders[$e]=$HOME/
only basic indexing=true
```

So on some stage of (9) step some component adds that additional "/home/<username> Indexed" item. That's the point of bug.
Let a user to manage the list without malware-like behavior of constantly added of the "/home/<username> Indexed" (so non-removable) item.

It is not about config: `~/.config/baloofilerc` does not rule that unwanted silent behavior. Most probably it is hard-coded.

---
Current System Info:
```
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.0-0-MANJARO (64-bit)
Graphics Platform: X11
```

Are there any more questions?


Thanks!

(In reply to pveax from comment #7)
> But I have that /home/<username> item in the `Folder specific
> configuration:` list.
Yes, I have that visible in the System Settings > Search but not there in .config/baloofilerc.

Then when you change the "Indexed" to "Not Indexed" in System Settings, baloofilerc is changed to:

> [General]
> dbVersion=2
> exclude filters=<hidden>
> exclude filters version=8
> only basic indexing=true
And then you get your:

> 10. Now I see that 2 items are listed:
> /home/<username> Indexed
> /home/<username> Not indexed
in the GUI and the only way of getting out of the problem is to manually edit the baloofilerc.

Yes, it's reproducable and I get the same on Neon Unstable.

(In reply to tagwerk19 from comment #8)
> Then when you change the "Indexed" to "Not Indexed" in System Settings,
> baloofilerc is changed to:
> 
> > [General]
> > dbVersion=2
> > exclude filters=<hidden>
> > exclude filters version=8
> > only basic indexing=true
Apologies...
Cut and paste problem, should read baloofilerc is changed to:

> [General]
> dbVersion=2
> exclude filters=<hidden>
> exclude filters version=8
> exclude folders[$e]=$HOME/
> only basic indexing=true

>and the only way of getting out of the problem is to manually edit the baloofilerc.

No, the problem in that very issue is that
'/home/<username>' with 'indexed' value
can not be removed:
neither via GUI,
nor via the `~/.config/baloofilerc` config file.

That's the point if the issue as it's title says that:
```
Settings -> File search: Folder specific configuration list: self-reproducing, irremovable items of '/home/<username>' with 'indexed' value
```

If you have another issue, open another bug report, please, do not change that issue description to the one you meet.

Thank you!

(In reply to pveax from comment #10)
> No, the problem in that very issue is that
> '/home/<username>' with 'indexed' value
> can not be removed:
> neither via GUI,
> nor via the `~/.config/baloofilerc` config file.
My apologies.

I'd got hooked on the issue that you could end up with both an "indexed" and a "not-indexed" entry. A case study in "not quite understanding" the report :-/

Sorry for my English.

```
$ balooctl status
Baloo is currently disabled. To enable, please run balooctl enable
$ balooctl config show includeFolders
/home/m/
$ balooctl config rm includeFolders /home/m
$ balooctl config rm includeFolders /home/m/
$ balooctl config show includeFolders
/home/m/
$ balooctl -v
baloo 5.86.0
$
```

Unable to remove a user home folder via TUI also.

Got the update, now it is
```
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.15.0-1-MANJARO (64-bit)
Graphics Platform: X11
```
and
```
$ balooctl -v
baloo 5.87.0
```
but it still can't remove the item.

*** Bug 439403 has been marked as a duplicate of this bug. ***

Still not fixed in Plasma version 6.2.3