Fix is
>sudo chmod -x /bin/baloo_file_extractor
...just have no words how I'm tired of it ....
]]>I installed baloo, this is on my laptop in sig. It's a 5 years old machine, with a recent SSD installed.
I don't have many files tho.
Baloo has worked flawlessly so far. It provides useful features and I was able to stop using the FSrunner Krunner which was vital for replacing what Nepomuk should have had.
So far so good.
I've recently installed KDE in three different laptops and no problems with those either.
In my opinion those having problems area very small very noisy minority. This does not mean that a disable button (with extended description on what features you are going to lose) should not be included, having choices is always better.
95% of the users will not even notice it tho and will just use their computers as they always did. People who believe 90% of KDE users are power users definitely do not see further than the end of their nose.
Hopefully this will come through in the next KDE update....
]]>My solution.
uninstall nepomuk
Disable Baloo
put your home dir in the blacklisting box in System Settings -> Desktop Search.
Disable Akonadi
Kdepim programs stop workin,i dont use any.
~/.config/akonadi/akonadiserverrc
StartServer=true >> StartServer=false
and optionary,be careful(del)
~/.kde4/share/config/(kresources)
~/.kde4/share/apps/(akonadi_migration_agent,kress-migration,korganizer)
~/.local/share/(akonadi,baloo,contacts,local-mail)
and reboot.
]]>I note that in the next version of KDE "On disabling Baloo, the baloo_file_cleaner would take some time in cleaning the database in 4.13.0. This has been fixed with 4.13.1, it now just directly deletes the database files."
At least that is some progress, but also from an upstream KDE bug the baloo author seems to be listening to the "feedback" on baloo, and says, "Guys, this is not the place to rant. I've re-opened the bug and may/may-not add an explicit button for 4.13.1." - again progress of a sort!
]]>It seems to have most of the options of the old Nepomuk KCM: whitelist for folders, ignore files by mimetype and regexp and suspending the service. Haven't really tried suspending, so I can't tell you how and if that works, but the rest works just fine.
]]>Adding /home to the blacklist causes Baloo to use very to no HD resources at all, but now jbd2/dm-3-8 is using 60% of HD resources.
Same for me. Added $home folder to the no-search list and these are the top processes for me now:
sudo iotop -a
34.70% [jbd2/sda7-8]
5.76% baloo_file_cleaner
2.10% [jbd2/sda6-8]
baloo should be an optional package, as long as this package can trigger serious lags on a modest PC configuration ( hard disk and not SSD, slow CPU )
]]>Please vote!
]]>Yeah I find all the fuzz incredibly weird as well, seems like most people complaining didn't use nepomuk anyway, and now have a huge problem with disabling the new engine for some reason, despite the myriad of possibilities mentioned practically everywhere (except for a dedicated button), and decide the best course of action would be ranting all over the place instead of using one of the ways to disable it and go on with their lives, but whatever.
So you complain that users "rant all over the place" instead of disabling it and go on with their lives, and yet you decide that the best course of action would be to rant about that? How about going on with your life instead?
]]>EDIT: plasma-desktop crashes when I try to log in with milou widget enabled, so nevermind.
]]>"
[13:14] <obsed> well baloo and others will get better in afew years after everyone has bug tested them, then they will be features users rave about
[13:14] <obsed> and if they let you disable them now then no one would bug test them enough
[13:14] <obsed> this is good for the progress of kde
[13:22] <obsed> mva: and baloo is better than the older nepomuk, its better at stopping you from disabling it
"
I hope this way sarcastic.
]]>