SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't know. I haven't had a problem with it for a long time, and I don't know if I've heard of others having the same problem. I've been doing some heavy space clearing in $HOME today, so maybe that's why it started causing problems again. I bet a lot of people have this issue without realizing it, though.
I wonder if you happen to use dolphin, maybe it takes it upon itself to re-enable baloo indexing services? This is also why I am wondering if perhaps this is a system type of setting and may need to issue the same command as root? I don't know.
I wonder if you happen to use dolphin, maybe it takes it upon itself to re-enable baloo indexing services? This is also why I am wondering if perhaps this is a system type of setting and may need to issue the same command as root? I don't know.
Apparently removing baloo_file isn't a good idea. It won't work at all if you do that. I reinstalled, purged the index, disabled, and re-enabled baloo, and now it's working again and so far not indexing file content. I fully expect it to start doing that again at some point, though.
Last edited by montagdude; 10-08-2021 at 12:21 PM.
Apparently removing baloo_file isn't a good idea. It won't work at all if you do that. I reinstalled, purged the index, disabled, and re-enabled baloo, and now it's working again and so far not indexing file content. I fully expect it to start doing that again at some point, though.
No it isn't sadly, dolphin whines when you launch it - hell you even get an error already when starting up Plasma5 - at least I did. It is shit like this that annoys me, the devs of say GNOME and KDE effectively deciding whats best for you.
No it isn't sadly, dolphin whines when you launch it - hell you even get an error already when starting up Plasma5 - at least I did. It is shit like this that annoys me, the devs of say GNOME and KDE effectively deciding whats best for you.
Contrary, they effectively deciding what's best for the most Plasma5 users.
You are the one who tries to use Plasma5 in ways isn't supposed to be - what happened with "use the right tool for the right job" ?
I will never understand your years long struggle with what are in fact core services of Plasma5 - both Akonadi and Baloo.
For what? To economize 400MB memory, which will be eaten by Firefox or Chromium when you open a news site?
I never bothered with 1GB memory eaten by Plasma5 or XFCE (or the 2GB memory eaten by Windows 10) because the major memory hogs are the web browsers - in a light browsing session of mine, the Firefox eats around 3GB, but with a bit of insistence, I can go it to 12GB.
OR, another memory hogs are the Development Editors - Darth Vader loved KDE4 because its Kate eaten "only" 8GB memory, compared with 24GB memory eaten by Kate of Plasma5 on early releases. Of course, this happening on his workflow.
And probably there are tons of another examples...
Anyway, I apologize for this rant in advance - feel free to go back to fighting windmills.
Last edited by LuckyCyborg; 10-08-2021 at 01:30 PM.
Contrary, they effectively deciding what's best for the most Plasma5 users.
You are the one who tries to use Plasma5 in ways isn't supposed to be.
I will never understand your this years long struggle with what are in fact core services of Plasma5 - both Akonadi and Baloo.
For what? To economize 400MB memory, which will be eaten by Firefox or Chromium when you open a news site?
I never bothered with 1GB memory eaten by Plasma5 (or the 2GB memory eaten by Windows 10) because the major memory hogs are the web browser - in a light browsing session the Firefox eats around 3GB, but with a bit of insistence, I can go it to 12GB.
OR, another memory hogs are the Development Editors - Darth Vader loved KDE4 because its Kate eaten "only" 8GB memory, compared with 24GB memory by Kate of Plasma5. Of course, on his workflow.
And probably there are tons of another examples...
Anyway, I apologize for this rant in advance - feel free to go back to fighting windmills.
Yea but why does it bother you how I use my system? As for the developers - they are not infallible; they should also at least offer the option to opt out certain things if you want to, thats all. Otherwise - why even bother? I can just go back to Windows then if I am to be dictated on "the right way" to use software.
I will never understand your years long struggle with what are in fact core services of Plasma5 - both Akonadi and Baloo.
For what? To economize 400MB memory, which will be eaten by Firefox or Chromium when you open a news site?
If you had read my earlier posts, you would know that my complaint is about it killing my system performance via extremely aggressive disk writing, not about 400 MB of memory. Also the fact that it starts running even though I've disabled it through the interface that the developers themselves provided. So spare me your soapbox rant.
Last edited by montagdude; 10-08-2021 at 01:34 PM.
If you had read my earlier posts, you would know that my complaint is about it killing my system performance via extremely aggressive disk writing, not about 400 MB of memory. Also the fact that it starts running even though I've disabled it through the interface that the developers themselves provided. So spare me your soapbox rant.
Then, how you explain that I do not experience "extremely aggressive disk writing" while using the Plasma5 in a full install of Slackware64 -current?
The system is installed on a Sandisk Extreme SD-card of 64GB, with the root partition formatted as F2FS and hosted in an USB 3.0 SD-card adapter. Meanwhile, I have prepared a quite small USB 3.0 SSD enclosure which hosts a drive of 120GB in a 2242 format, on "waiting" as replacement, because I have become habituated with this SD-card and I am also curious how much time it will survive.
The computer itself is a MinisForum Z83-F with a quad-core Intel Atom x5-Z8350 up to 1.92 GHz and 4GB memory DDR3 at 1066MHz. It have also an eMMC of 64GB which host its original Windows 10 Pro.
The mini-PC looks like in the attached image, which I grabbed from their site.
This setup works fine since almost 2 years, and I guess that this "extremely aggressive disk writing" you mention would/could be extremely dangerous for my SD-card life expectancy. And let's do not talk about system performances of a 2W CPU, there's not much to kill.
So, how you explain that you experience the "killing of your system performance" on a probably much better box, while on my little computer the full installed Plasma5 works quite fine? It even has the Akonadi and Baloo with their defaults.
Could be that you do something wrong or you experience a hardware issue?
I heard that a bad SATA cable can produce strange system freezes even on a little disk load. Just an example.
Last edited by ZhaoLin1457; 10-08-2021 at 04:10 PM.
If you go to the system settings control panel in plasma 5, click search, and uncheck the "enable file search" box, it disables baloo. I've had that checked for all of 2021 and I havent seen baloo since. There are the balooctl and baloofilerc config file methods to disable it but this one seems to stick consistently.
Edit: Any chance you mounted some storage in your $HOME while cleaning it up? I've had baloo eat my performance in that situation like that but that was in ktown days. Now I dont bother with it since I don't have much use for it.
Then, how you explain that I do not experience "extremely aggressive disk writing" while using the Plasma5 in a full install of Slackware64 -current?
The system is installed on a Sandisk Extreme SD-card of 64GB, with the root partition formatted as F2FS and hosted in an USB 3.0 SD-card adapter. Meanwhile, I have prepared a quite small USB 3.0 SSD enclosure which hosts a drive of 120GB in a 2242 format, on "waiting" as replacement, because I have become habituated with this SD-card and I am also curious how much time it will survive.
The computer itself is a MinisForum Z83-F with a quad-core Intel Atom x5-Z8350 up to 1.92 GHz and 4GB memory DDR3 at 1066MHz. It have also an eMMC of 64GB which host its original Windows 10 Pro.
The mini-PC looks like in the attached image, which I grabbed from their site.
This setup works fine since almost 2 years, and I guess that this "extremely aggressive disk writing" you mention would/could be extremely dangerous for my SD-card life expectancy. And let's do not talk about system performances of a 2W CPU, there's not much to kill.
So, how you explain that you experience the "killing of your system performance" on a probably much better box, while on my little computer the full installed Plasma5 works quite fine? It even has the Akonadi and Baloo with their defaults.
Could be that you do something wrong or you experience a hardware issue?
I heard that a bad SATA cable can produce strange system freezes even on a little disk load. Just an example.
Whenever this happens, my system becomes extremely sluggish. We're talking 5 seconds to open a new konsole window, for example. I see that baloo_file is indexing files and using lots of CPU, RAM, and disk writing. I kill it, and the problem goes away. I never have problems with this system otherwise. It's very clear that the Baloo file indexer is the problem. Maybe you don't notice it because you are not using an HDD. Besides, it shouldn't start indexing file content when I tell it not to. You're gaslighting and should just go away if you don't have anything helpful to offer.
If you go to the system settings control panel in plasma 5, click search, and uncheck the "enable file search" box, it disables baloo. I've had that checked for all of 2021 and I havent seen baloo since. There are the balooctl and baloofilerc config file methods to disable it but this one seems to stick consistently.
That's exactly what I do. Even while it's going on, the system settings module still shows it as disabled.
Quote:
Originally Posted by 0XBF
Edit: Any chance you mounted some storage in your $HOME while cleaning it up? I've had baloo eat my performance in that situation like that but that was in ktown days. Now I dont bother with it since I don't have much use for it.
Whenever this happens, my system becomes extremely sluggish. We're talking 5 seconds to open a new konsole window, for example. I see that baloo_file is indexing files and using lots of CPU, RAM, and disk writing.
And how many files tries this poor Baloo to index in your home? Hundreds? Thousands? Trillions?
I ask because I suspect that you have many, many but really many files in your $HOME.
I for one, I preffered always to put the data out of $HOME - practically I have /data/users/$user where every user puts its valuable data.
With a bit of attention, I matched the UIDs with openSUSE, then I have a common data place for the user from Slackware and openSUSE. It's very handily.
Still, the point of a bad SATA cable is real. Those are really nasty witches. I had several past experiences with them.
Quote:
Originally Posted by montagdude
I kill it, and the problem goes away. I never have problems with this system otherwise. It's very clear that the Baloo file indexer is the problem.
Honestly, I cannot reproduce your Baloo issue. And I tried hard this evening.
That's WHY I wonder how clean is your system.
So, you can reproduce your issue with a different SATA cable, different hard drive (even it's an old 5400 RPM for laptops) and a fresh clean Slackware -current install? And with a clean new user, with no tons of data on it?
Quote:
Originally Posted by montagdude
Maybe you don't notice it because you are not using an HDD.
Uh, oh...
The SD-cards aren't the best storage devices on the wild, you know. Looking at this page:
looks like he lives with 90MB/s read and 45MB/s write on his storage device. The speeds are similar with a 5400 RPM hard drive, but probably with better seek times and certainly with much worst endurance.
I believe that IF ever he will experience your issue, this SD-card of him probably will be dead on matter of minutes.
Quote:
Originally Posted by montagdude
Besides, it shouldn't start indexing file content when I tell it not to.
That's WHY I believe that your system is quite dirty. Or maybe also you have also a nice partial install?
Long story short, no one of my boxes experiences this phenomena, and they host Slackware -current installations of different ages.
Quote:
Originally Posted by montagdude
You're gaslighting and should just go away if you don't have anything helpful to offer.
With all respect, there you jumped way over horse. It's NOT your personal thread where to debate exclusively your particular Baloo issue.
IF anything, his story is a nice success story of Plasma5 on a low power mini-PC. So, according with the thread title: "All Things KDE5/Plasma for Slackware Users." is quite on topic.
However, he given you a testimony that he does not experiences your particular issues with Baloo.
Also, myself I testify this, from my own experience. And there are others saying the same from their own experiences.
In my humble opinion, if anything this is useful for you to square where the issue is for real.
Last edited by LuckyCyborg; 10-08-2021 at 06:40 PM.
And how many files tries this poor Baloo to index in your home? Hundreds? Thousands? Trillions?
I ask because I suspect that you have many, many but really many files in your $HOME.
I for one, I preffered always to put the data out of $HOME - practically I have /data/users/$user where every user puts its valuable data.
So in order for baloo not to go crazy, I have to use some unusual layout where I put most of my stuff on a separate partition? Doesn't sound too user friendly. My $HOME is something like 160 GB worth of files. That's not anything unusual.
Quote:
Originally Posted by LuckyCyborg
Honestly, I cannot reproduce your Baloo issue. And I tried hard this evening.
That doesn't surprise me. Like I said, this only happens infrequently. No, I cannot reproduce the issue on demand, but it has happened to me probably half a dozen times over the last few years. It has very clear symptoms and a very clear way to stop it when it does (by killing baloo_file).
Quote:
Originally Posted by LuckyCyborg
With all respect, there you jumped way over horse. It's NOT your personal thread where to debate exclusively your particular Baloo issue.
I made a post noting the issue and how I worked around it. That is completely on topic for this thread. Then I got a bunch of obnoxious posts from you and ZhaoLin1457 claiming there is no issue and that it must be my fault, as if I somehow personally insulted you by reporting this issue. You are the ones out of line. If you would stop blaming me for something that is obviously a baloo bug, I would stop having to defend myself.
Quote:
Originally Posted by LuckyCyborg
In my humble opinion, if anything this is useful for you to square where the issue is for real.
The issue is that baloo is indexing file content when I explicitly disabled that feature. End of story. I did not do anything that should reasonably have caused that to happen. It was even running while my system settings said it was disabled. If you have anything to offer other than "it works for me" -- which is completely useless advice in this case -- then please let me know. On the other hand, if you are just going to keep blaming me for nebulous reasons that you can't actually articulate, then kindly stop posting about this. I am glad no one else is having this issue, or at least hasn't noticed it, but that doesn't mean there is no issue.
Personally, I'm done talking about this since it's too hard to reproduce to file a bug report anyway. Let's just move on.
Last edited by montagdude; 10-08-2021 at 09:47 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
