This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Baloo not indexing all files, even after a "balooctl check"

Tags: None
(comma "," separated)
molecule-eye
Registered Member
Posts
402
Karma
0
OS
"balooctl status" shows:

Baloo File Indexer is running
Indexer state: Idle
Indexed 9636 / 10077 files
Current size of index is 707.54 MiB

So there are over 400 files that are NOT indexed. So of course I ran "balooctl check" which is supposed to "Check for any unindexed files and index them", but it doesn't do anything. I checked about 5 minutes later and the status is the same. I don't want to reindex everything (which I"ve had to do several times already with baloo in the past). Is there any way to force a check and index?
molecule-eye
Registered Member
Posts
402
Karma
0
OS
I just tried to manually index the file I noticed wasn't indexed and I got a message saying that the file is being skipped as it's "already schedule for indexing". Nothing I can do will force it to index the dang file!
koffeinfriedhof
Registered Member
Posts
608
Karma
4
OS
Hi!

At first you should check the file permissions!

To force baloo to index all files (again) you could do the following:
[*]stop baloo with `balooctl disable`
[*]change your .config/baloofilerc and set initialIndexingDone=false
[*]restart baloo with `balooctl enable; balooctl check`
ozone
Registered Member
Posts
14
Karma
0
In order to get the missing 400 files indexed, and since you already identified the culprit: You could just add the name of your file to the exclude filter in baloofilerc. But note this may have side effects, in case there are several files with the same name on your system.

I guess it would be interesting to see if this is reproducible on another system (e.g. in a virtual machine). If your feeling of privacy permits - I would file a proper bug report.

Last edited by ozone on Mon Nov 27, 2017 1:25 am, edited 1 time in total.
User avatar
jayesh.bhoot
Registered Member
Posts
3
Karma
0
OS
molecule-eye wrote:I just tried to manually index the file I noticed wasn't indexed and I got a message saying that the file is being skipped as it's "already schedule for indexing". Nothing I can do will force it to index the dang file!


How do you find which files are not being indexed? I am pulling my hair out on this.
ozone
Registered Member
Posts
14
Karma
0
Issues could be related to https://forum.kde.org/viewtopic.php?f=154&t=133584.

jayesh.bhoot wrote:How do you find which files are not being indexed? I am pulling my hair out on this.


If baloo "hangs" because of only one particular file, you should find it with:
Code: Select all
qdbus org.kde.baloo /fileindexer org.kde.baloo.fileindexer.currentFile


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]