Bug#1120628: baloo6: Disabling baloo by default results in a confusing user experience
Le 17 novembre 2025 15:13:20 GMT+01:00, Celejar <celejar@gmail.com> a écrit :
>On Mon, 17 Nov 2025 00:10:41 +0100
>Aurélien COUDERC <libre@coucouf.fr> wrote:
>
>> Hi,
>>
>> Le jeudi 13 novembre 2025, 17:36:02 heure normale d’Europe centrale Celejar a écrit :
>> >
>> > I recently tried to get KDE/Plasma File Search working. Through the
>> > KDE/Plasma UI, I enabled "File indexing" and set "Data to index: File
>> > names and contents" - and nothing happened. The KDE interface status
>> > line reported "Not Running, 0% complete", but gave no explanation as to
>> > why the indexer wasn't running despite "File indexing" being enabled.
>>
>> I think there’s a misunderstanding about what the "Not Running, 0%
>> complete" tries to convey.
>
>> This message only means that the indexer is not running *at that
>> particular time*, and the underlying meaning is that there’s nothing to
>> do because indexing was already done.
>
>"0% complete" means that "there's nothing to do because indexing was
>already done"? If so, that's a really poorly worded message.
No you're right, I overlooked your message because I was seeing the same but with 100% on my machine.
>> The File indexing checkbox does enable and disable baloo in the same
>> way as the balooctl command does.
>
>It does? As I reported above, "File indexing" is checked, "Data to
>index" is set to "File names and contents", but:
>
>~# balooctl6 status
>Baloo is currently disabled. To enable, please run balooctl enable
OK strange then I will retry again but I'm pretty sure I was getting baloo activated / deactivated consistently with what I chose in the UI.
Could you try running systemsettings from a terminal and see if you get more info when changing the search config ?
Thanks,
--
Aurélien
Reply to: