Skip to main content ↑ ↓
Topic: "baloo_file_extractor Closed Unexpectedly" (Read 1397 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

"baloo_file_extractor Closed Unexpectedly"

I get this annunciation right after log-in
"baloo_file_extractor Closed Unexpectedly...please
report this error to help improve this software"

without seeing any adverse behavior beyond.

tried to 'attach' baloo-extractor.png (34.27 KB),
it selected but showed only ghosted very pale in
the dialogue and no button to 'place inline', only
a trashcan to junk it.

Addendum 2022-10-31
- screenshot deleted
- subject prob still there on every boot exactly as it was

--
Artix Linux , Kernel=5.16.7-artix1-1 on x86_64,
DM=Unknown, DE=KDE, ST=x11,grub2, GPT, BIOS-boot

Who, has loved us more?

Re: "baloo_file_extractor Closed Unexpectedly"

Reply #1 –
Why is there a huge, distracting screenshot in your post? Meanwhile, the screenshot of an error is tiny in comparison. If you mean to include that screenshot as part of your "signature" on a regular basis, please rethink that.

Have you considered pressing "Report Bug" to send the bug report upstream instead of posting here?

Re: "baloo_file_extractor Closed Unexpectedly"

Reply #2 –
I read the solution is to delete the baloo cache at: ~/.local/share/baloo

Make a backup of it before deleting just in case.
Chris Cromer

Re: "baloo_file_extractor Closed Unexpectedly"

Reply #3 –
Quote from: strajder – on
Why is there a huge, distracting screenshot in your post? Meanwhile, the screenshot of an error is tiny in comparison. If you mean to include that screenshot as part of your "signature" on a regular basis, please rethink that.

Have you considered pressing "Report Bug" to send the bug report upstream instead of posting here?

No, my sig will never be a screen shot

Yes, I not only considered it but actually clicked it to be informed that there was nothing to do because....whatever

I only cited it in case some dev would be interested, personally I really don't give seeing that as I said it meant no adverse behavior




 
Who, has loved us more?

Re: "baloo_file_extractor Closed Unexpectedly"

Reply #4 –
Quote from: Chris Cromer – on
I read the solution is to delete the baloo cache at: ~/.local/share/baloo

Make a backup of it before deleting just in case.

There was no cache only 2 files: index & index-lock
Deleted both, they were regenerated next boot.
Same annunciation by KDE crash handler.

Who, has loved us more?

Re: "baloo_file_extractor Closed Unexpectedly"

Reply #6 –
Quote from: tintin – on
Hello,
Maybe a solution here:
https://www.kubuntuforums.net/forum/currently-supported-releases/kubuntu-20-04-focal-fossa-lts/software-support/71420-baloo-file-indexing-daemon-closed-unexpectedly

Merci!

That does it, seems like something not ready for prime-time. I would never have thought of killing it because being Suse-spoiled I run away scared when Yast tells me that "baloo is a must, or forget Plasma" :-)

Nonetheless on my end I've only seen it with this, my Artix (Plasma iso installed) system. Seeing that the failure is just a nuisance I think I'll let it ride for now.


--
https://i.imgur.com/b6voLxD.png
Who, has loved us more?