biasquez wrote:

Naproxeno wrote:

biasquez wrote:it seems that natty with kdepim 4.6 beta 4 has this patch

Do you know if Maverick has also this patch applied?

i don't know...do you have kdepim 4.6 or 4.5?

I have installed the package "4:4.5.94.1-0ubuntu1~maverick1~ppa1" so I guess I have 4.6 beta.

If this version has also the patch I think I should try with a fresh .kde directory to test if it's a configuration problem.

There has been some activity today regarding this bug and it seems Sebastian has commited a patch (the same patch referred to here?) to avoid the CPU problem.

Let's hope it works as expected in the final release of KDE 4.6.

einar wrote:Did you also disable "Nepomuk Search" along with "Contacts"?

Ok, this advice along with disabling Contacts in KRunner helped, no more crazy virtuoso processes in the last couple of days.

I will leave this thread unresolved for a little while longer, so that other folks can also find a solution, which would work for them.

Hopefully, the proposed patch will work and will be soon included into the 4.6 branch.

Thanks again einar for your help.

It seems Sebastian solved the issue (https://bugs.kde.org/show_bug.cgi?id=246678) probably on the stable release we won't have to use the little tweak to avoid virtuoso going crazy.

Regards

With KDE 4.6.0 pre-release packages, I can drive Virtuoso crazy with the "Nepomuk Search" KRunner plugin, but not with "Contacts". So, I can use "Contacts" safely.

On that topic: patches that improve the behavior are still being refined. The reason is not the fix itself (they work already), but rather avoiding a large and CPU intensive conversion time on first run (~ 30 minutes).

einar wrote:On that topic: patches that improve the behavior are still being refined. The reason is not the fix itself (they work already), but rather avoiding a large and CPU intensive conversion time on first run (~ 30 minutes).

Even if they don't fix that amount of time... I can live with that

Regards

If you're interested in patching things yourself, patches are available at Bug #246678.