Registered Member
|
Hi folks,
I have always kept Strigi disabled, never liked the resources it ate and never used any of its features. However, after upgrading to 4.6-rc1, I found that two, not one, strigidaemon instances were started automatically, eating up my dual core. If I kill them, after a while Akonadi complains it's not running and it is started again (by whom I do not know). I don't want to have to rename the binary, can this be fixed in any other way? Cheers GODLiKE |
Administrator
|
Open "akonadiconsole", and remove the "Strigi Indexer" from it. This is used by Akonadi to index emails on low performance platforms such as Mobile Phones, and is unintentionally enabled on the Desktop I believe.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for the info, I will try it today when I get home.
|
Registered Member
|
A few days with the fix and still nothing unusual or undesireable, so I think this fixed it.
EDIT: woops, talked to early. It's on again like nothing happened |
Administrator
|
Akonadi has a habit of reverting this fix, so you may need to re-apply it.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Administrator
|
Also please disable the "nepomuksearch" and the "Contacts" runners in krunner, as queries from these two plugins trigger other bugs in the underlying infrastructure, that lead the Nepomuk server into an unrecoverable state (100% CPU).
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
What a mess! It's quite irritating to find that you've suddenly got an hour of battery life on a full charge, expecting at least 4 hours, because of some unwanted strigidaemon initializing whenever it wants with no indication of what's going on because of a lack of tray icon.
This is definitely the buggiest RC I've encountered yet. |
Registered Member
|
I guess there is a reason why it's called RC. Sorry if I misunderstood, but shouldn't you be using something a bit more stable for actual work? (obviously doesn't apply if you're a KDE developer) |
Registered Member
|
To prevent strigidaemon from eating your CPU and launching itself unwantedly:
1) open akonadiconsole 2) remove any "strigi" feeder 3) check that the strigifeeder.desktop file (mine is at /usr/share/akonadi/agents/strigifeeder.desktop ) does NOT contain "Autostart" done ... |
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]