This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Fedora crashes with baloo errors in journatctl.

Tags: None
(comma "," separated)
daddyodevil
Registered Member
Posts
1
Karma
0
I have Fedora 35 with the latest updates of KDE. I have 10s of TBs of storage attached to my system, both by internal and external HDDs. So Baloo indexing service would end up taking above 30 GB of RAM. I have tried to disable Baloo but I think I didn't do it probably. My system crashes about twice or thrice every week. Everything stops working. Only a reboot solves it.
The journalctl messages shows a Baloo error, and it just continues forever.
Images here -

https://imgur.com/Z8fXDUy

https://imgur.com/4rnGREU

https://imgur.com/o2Wgz8L

https://imgur.com/gY6ilb9

https://imgur.com/a/FCwJzt8
User avatar
Mamarok
Manager
Posts
6071
Karma
16
OS
FWIW, pasting text files as actual text would have been easier than screenshots...

Anyway, try to run this:
Code: Select all
balooctl suspend
balooctl disable

This should stop and disable Baloo on the next reboot (you need to reboot for the disable to take effect).
If you want to erase the index, run
Code: Select all
balooctl purge


You can find all necessary information on how to debug Baloo in our wiki: https://community.kde.org/Baloo/Debugging


Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ...


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kesang, Yahoo [Bot]