Kann es sein, dass es ein i386-Problem ist? Schaut mal, ich habe vor enable/disable den Status angeguckt, und danach mehrmal in etwa 5-Sekunden-Intervallen. Es bleibt immer an (fast) der selben Stelle hängen:
$ balooctl status
Baloo File Indexer is running
Indexer state: Inaktiv
Indexed 6641 / 98100 files
Current size of index is 67,19 MiB
$ balooctl disable
Disabling the File Indexer
$ balooctl enable
Enabling the File Indexer
hans@thinkboxX201:~$ org.kde.baloo: "/home/hans"
Power state changed
$ balooctl status
Baloo File Indexer is running
Indexer state: Erstindizierung
Indexed 0 / 0 files
Current size of index is 12,00 KiB
$ balooctl status
Baloo File Indexer is running
Indexer state: Erstindizierung
Indexed 0 / 0 files
Current size of index is 12,00 KiB
$ balooctl status
Baloo File Indexer is running
Indexer state: Erstindizierung
Indexed 0 / 0 files
Current size of index is 12,00 KiB
$ balooctl status
Baloo File Indexer is running
Indexer state: Inaktiv
Indexed 6642 / 98100 files
Current size of index is 67,21 MiB
$ balooctl status
Baloo File Indexer is running
Indexer state: Inaktiv
Indexed 6642 / 98100 files
Current size of index is 67,21 MiB
$ balooctl status
Baloo File Indexer is running
Indexer state: Inaktiv
Indexed 6642 / 98100 files
Current size of index is 67,21 MiB
(i386 bei mir)