You are not logged in.
in kde 4.8.1 still the same. virtuoso eats all cpu.
Offline
The foolproof solution is to backup and remove the nepomuk database. Something to do with having an old database that's gone through various upgrades seems to cause this problem, I think.
Offline
i deleted the ~/.kde4/share/apps/nepomuk folder after the update to 4.8.1
but no difference
Offline
Have you seen this blog post? It might help you identify the culprit:
http://vhanda.in/blog/2012/02/virtuoso-going-crazy-/
Offline
maybe i should have wait a bit. now, after 2 hours of high cpu usage it's lowered down to 10-30% and my fan keeps quiet.
[EDIT] after half an hour high cpu usage started again and is still in progress
qdbus org.kde.nepomuk.services.nepomukqueryservice
/
/nepomukqueryservice
/servicecontrolit shows no queries like in the post http://vhanda.in/blog/2012/02/virtuoso-going-crazy-/
Last edited by mongohorst (2012-03-09 00:55:21)
Offline
KDE 4.8.1 here, and high cpu usage started a few days ago on my laptop eating battery like crazy.
- Virtuoso seems to be the culprit according to htop.
- Disabling nepomuk in system settings has no effect on cpu usage
- Following the "virtuoso going crazy" blog, I don't have any specific query showing up
- Looking at akonadi console the only active agent is "akonadi nepomuk feeder" indexing an imap mailbox and seems stuck at 89%
After some fiddling, disabling/enabling this and that, I was about to remove the virtuoso db and nepomuk db when the fan got back to normal and suddenly cpu usage is normal again, I noticed "akonadi nepomuk feeder" now says indexing complete.
Offline
Just had another outbreak of virtuoso eating cpu, albeit a different one this time.
I was writing an email in kmail when the fan started being noisy, then the kmail window became unresponsive and turned gray.
Trying to access desktop search option from system setting didn't work and akonadiconsole gave this error.
akonadiconsole
"/usr/bin/akonadiconsole(32655)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."Trying to list the service failed too:
qdbus org.kde.nepomuk.services.nepomukqueryservice
Could not connect to D-Bus server: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.After a SIGKILL and disabling of mail indexing, cpu usage is back to normal.
Offline