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.
The basic indexing setting works most of the time, it's just that every once in awhile the file content indexes starts up again on without being asked to. Today it happened after a restart to fix a strange sddm issue that had appeared, but I don't have any reason to believe the two problems are related. I guess I will leave baloo_file_extractor around on the off chance I might be able to figure out why that happens eventually.
Last edited by montagdude; 03-31-2020 at 08:04 PM.
Reason: Typo
The basic indexing setting works most of the time, it's just that every once in awhile the file content indexes starts up again on without being asked to. Today it happened after a restart to fix a strange sddm issue that had appeared, but I don't have any reason to believe the two problems are related. I guess I will leave baloo_file_extractor around on the off chance I might be able to figure out why that happens eventually.
I know this would just be a bandaid fix if it works, but have you tried simply removing the execute permission on /usr/bin/baloo_file_extractor?
Would it be possible to start baloo_file_extractor with ionice so it will only do indexing when HD is not in heavy use by other things?
Maybe a wrapper script?
I'm sure there are a number of workarounds to prevent it from starting up, but they would all have to be reapplied when Eric upgrades the package. It happens rarely enough and with obvious enough symptoms that going forward I can just deal with it when it happens. My larger concern is that this will happen to people when Slackware 15 comes out and they won't have a clue why, and probably just assume that Slackware and/or Plasma 5 is really slow.
I think I will bump this thread every time baloo_file_extractor decides to start up again despite being disabled. This is #2.
#3. It seems to happen after a reboot, but I don't think every reboot. I'll test that out some more. If I can reproduce it, maybe I can file a bug report upstream.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'll test that out some more. If I can reproduce it, maybe I can file a bug report upstream.
