Bug 377302 - Baloo keeps some removed files in the index
Summary: Baloo keeps some removed files in the index
Status: RESOLVED DUPLICATE of bug 353874
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.32.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-06 18:02 UTC by FabiB
Modified: 2017-10-27 20:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description FabiB 2017-03-06 18:02:05 UTC
I'm a heavy user of baloo. Settings tags to files, searching via krunner / dolphin, Using tag-directory widgets on the desktop

Its a great thing to have something like baloo! Thanks for this.

However the index needs a cleanup functionality. Usually I delete my ~/.local/share/baloo/index every 2 month. Because baloo adds stuff to the index just fine, but don't delets them properly.

I can still find the content of my ~/Downloads/linux4.8 directory that is not there anymore for.. uhm when was 4.9 released? 

In numbers:

before ~/.local/share/baloo/index deletion

balooctl status
Baloo File Indexer is running
Indexer state: Idle
Indexed 29582 / 29582 files
Current size of index is 176,30 MiB

after:

Baloo File Indexer is running
Indexer state: Idle
Indexed 7535 / 7535 files
Current size of index is 31,14 MiB

wich is near the truth
find ~ /home/share/Musik -type f -not -path "*/.*" -not -path "*/Projekte/GIT/*" | wc -l 
7046

---

So it would be nice if baloo could run a check if a file still is available and if not - remove it from the index
Comment 1 Gennady Uraltsev 2017-03-27 12:32:38 UTC
Same thing here! 
$ balooctl --version
baloo 5.26.0

and old files don't get removed.
Comment 2 Gennady Uraltsev 2017-04-07 11:54:24 UTC
Can confirm on 5.26.0
Comment 3 hotmusicfan 2017-09-06 22:57:11 UTC
I can confirm it too (5.36).
Comment 4 Nate Graham 2017-10-27 20:14:51 UTC

*** This bug has been marked as a duplicate of bug 353874 ***