I don't need desktop file search so badly that I'm willing to endure constant 50% memory pressure and the riot the OOM killer brings because of it.

It's quite possible, even likely, that there's something misconfigured on my side, but that's the point. I wish this distribution would stop including (combinations of) features so sensitive to my goofs that it makes the computer unstable.

Ubuntu's lovely userspace OOM killer was targeting /user.slice/.../init.scope and killing my entire login session periodically throughout the day (and in the middle of the night if I left the computer on). It took me five days to figure out that kde-baloo.service was responsible for a constant 50% memory pressure even though there was plenty of free RAM, free swap, and swappiness was set pretty low, something I can't get my head around. Any time anything else kicked off that hit the RAM hard, OOM killer would wake up and say "time to murderrrrrr". For reasons I don't understand, rather than killing one or two RAM-hungry processes--like the culprit baloo!!!--it would rampage through my entire login session, even killing the desktop and window managers before it was sated.

So in essence, in order to have desktop file search I'd use maybe once a month, I'd have to suffer crashes of my login session several times a day. No thank you.

I stuck with KDE through the horrible nepomuk era, and at first baloo seemed better. But here we are again, disabling all traces of it.

(By the way, this is not a cry for help, a request for advice, a call to suggest Arch or *BSD or i3 or Xfce or anything else. I'm just venting).

#KDE #baloo #nepomuk #ubuntu #FileSearch