Understanding why baloo does not work?

Help
1

Hello,

this weekend I try to understand what baloo is doing, and why it is not doing what I think it is supposed to do.

My system is

Operating System: Arch Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

It has been sitting in idle (and battery powered) for ages.

The baloo settings are all default:

$ balooctl6 config list includeFolders 
/home/florian/

$ balooctl6 failed 
All Files were indexed successfully

$ balooctl6 config list excludeFolders

balooctl6 monitor on an idle system shows nothing after Inactive. Same when trying to explicitly index a file.

$ balooctl6 status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 872204
Files waiting for content indexing: 743791
Files failed to index: 0
Current size of index is 7.06 GiB

Looking at one specific file under /home/florian:

$ balooshow6 Kostenkalkulation.ods
13a4457301377f3 806582259 20595799 Kostenkalkulation.ods: No index information found 

$ balooctl6 index Kostenkalkulation.ods
[sitting for 5 minutes and counting]

What could I further do to find out what is wrong here and possibly fix it? I have tried to delete the index but that always leaves substantial parts of my files unindexed.

Best Thanks!

1 Like
2

Can you try using the full file path?

Something like this:

$ balooshow6 /home/florian/Kostenkalkulation.ods

And then, if needed:

$ balooctl6 index /home/florian/Kostenkalkulation.ods
3

Hey, this changes nothing

# florian @ osiris in ~ [10:36:20] C:1
$ balooshow6 /home/florian/Cloud.XGM/xxx/yyy/Kostenkalkulation.ods
13a4457301377f3 806582259 20595799 /home/florian/Cloud.XGM/xxx/yyy/Kostenkalkulation.ods: No index information found

# florian @ osiris in ~ [10:36:23] 
$ balooctl6 index /home/florian/Cloud.XGM/xxx/yyy/Kostenkalkulation.ods
[canceled by me after 5 minutes]

:frowning:

copying the file to $HOME/tests.ods yields the same results.

Curiously,

# florian @ osiris in ~ [10:43:59] C:130
$ balooctl6 index /home/florian/non_existing_file

shows the same behavior: no error message, just stalls

4

the index seems huge.

what are the results of?

balooctl6 indexSize

what are the results of?

balooctl6 config list hidden

when you tried deleting the index did you do all three of these?

balooctl6 disable

balooctl6 purge

balooctl6 enable

5 
$ balooctl6 indexSize
File Size: 7,06 GiB
Used:      938,46 MiB

           PostingDB:     282,04 MiB    30.054 %
          PositionDB:     309,65 MiB    32.995 %
            DocTerms:     139,67 MiB    14.883 %
    DocFilenameTerms:      58,99 MiB     6.286 %
       DocXattrTerms:            0 B     0.000 %
              IdTree:      17,59 MiB     1.875 %
          IdFileName:      65,35 MiB     6.963 %
             DocTime:      38,61 MiB     4.114 %
             DocData:     232,00 KiB     0.024 %
   ContentIndexingDB:      23,04 MiB     2.455 %
         FailedIdsDB:            0 B     0.000 %
             MTimeDB:       3,30 MiB     0.351 %

$ balooctl6 config list hidden
no

I will try to delete the index as described and report back.

6

It has been sitting in idle (and battery powered) for ages.

Baloo doesn’t do any indexing while on battery power, because it tries to avoid using resources and impacting your battery life. If you plug in the system, it should start indexing things again.

1 Like
7

Sorry, that was a typo in the original post. It was sitting idle and was powered (no battery).

8

After purging, it is still running, but it looks like that the progress has stalled:

Status from 14:57

$ balooctl6 status
Die Baloo-Dateiindizierung läuft
Indizierungsstatus: Inaktiv
Gesamtzahl der indizierten Dateien: 615.988
Dateien, die noch indiziert werden: 544.579
Dateien, deren Indizierung fehlgeschlagen ist: 0
Der aktuelle Index hat eine Größe von 462,48 MiB

Status from now 16:13 is still identical.

Though, the baloo_file_extractor process is running with around 15% load:

grafik
grafik843×191 34.7 KB

The machine was 95% idle during the last two hours. (really left alone, freshly booted, no expensive background processes)