SUMMARY If you disable baloo, you need to enable it twice... STEPS TO REPRODUCE: $ balooctl status Baloo File Indexer is running Indexer state: Idle $ balooctl disable Disabling and stopping the File Indexer $ balooctl status Baloo is currently disabled. To enable, please run balooctl enable $ balooctl enable Baloo File Indexing has been disabled Enabling and starting the File Indexer and then.... OBSERVED RESULTS $ balooctl status Baloo File Indexer is not running $ balooctl enable Enabling and starting the File Indexer $ balooctl status Baloo File Indexer is running Indexer state: Idle EXPECTED RESULTS $ balooctl status Baloo File Indexer is running Indexer state: Idle SOFTWARE/OS VERSIONS Neon Testing Baloo : 5.81.0 Plasma : 5.21.3 Frameworks : 5.81.0 Qt : 5.15.2 ADDITIONAL INFORMATION I think this has got lost somewhere between the cracks
Hmm, cannot reproduce.
That's pretty strange. I see reproducable behaviour. I did have a surprise though when I stepped through the "Steps to Reproduce" on a Neon Testing "Live" edition. Neon Testing 20210330 Live (5.81.0) balooctl disable balooctl enable Worked as it ought to.... Neon Testing 20210330 Installed (5.81.0) balooctl disable balooctl enable balooctl enable That second "enable" is needed... I looked back though a collection of older Neon Testing ISO's, it was the same behaviour (5.80.0, 5.79.0, 5.76.0, 5.72.0). A "Live" install worked but as soon as I installed to disc the behaviour changed and I needed to "balooctl enable" twice. The behaviour was the same with Installed-to-disc Fedora 33 and 34 Beta
Maybe interesting, on the "Live" image you don't get the "Baloo File Indexing has been disabled" message when enabling, it's just: $ balooctl disable Disabling and stopping the File Indexer $ balooctl enable Enabling and starting the File Indexer $ ps ax | grep baloo 1596 ? SNl 0:00 /usr/bin/baloo_file 1601 pts/1 S+ 0:00 grep --color=auto baloo