Re: Bug#1120628: baloo6: Disabling baloo by default results in a confusing user experience

[Celejar <celejar@gmail.com>]

On Mon, 17 Nov 2025 16:31:26 +0100
Aurélien COUDERC <libre@coucouf.fr> wrote:

> 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:

...

> >> 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 ?

I get this seemingly relevant message:

Error fetching Baloo indexer state: "Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken." 

> Thanks,
> --
> Aurélien

-- 
Celejar