This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Virtuoso backend goes crazy in 4.6 beta1

Tags: None
(comma "," separated)
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
einar wrote:Disable the contacts and nepomuksearch runners in KRunner (Alt-F2 > Wrench icon > untick "Nepomuk Search" and "Contacts"), and the problem should go away.


Not enough. I have disabled contacts in KRunner, unfortunately virtuoso-t processes still keep taking extensive cpu power.

Any other other ideas what and where to disable?

Thanks.
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
I forgot to tell that you need to log out and back in for this to make an effect as if virtuoso-t is already in its bad state, it can't be recovered. By logging out and back in you may trigger an unrelated 100% CPU bug in kded4, so it may be wiser to reboot.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
einar wrote:I forgot to tell that you need to log out and back in for this to make an effect as if virtuoso-t is already in its bad state, it can't be recovered. By logging out and back in you may trigger an unrelated 100% CPU bug in kded4, so it may be wiser to reboot.


I have actually rebooted several times already, just to be sure. After while of being logged in, several virtuoso-t processes start fighting for cpu. There must be something else other than contacts in krunner triggering it.

Could it be kopete with contacts linked to address book contacts? I will try to boot next time without kopete.
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
That may be as well the case. I have to point out that Sebastian Trueg cooked up a patch to fix at least the krunner side. I don't know if distros will incorporate it, however.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
Damnshock
Registered Member
Posts
111
Karma
0
OS
einar wrote:That may be as well the case. I have to point out that Sebastian Trueg cooked up a patch to fix at least the krunner side. I don't know if distros will incorporate it, however.


Could you point us to the patch? we may try it and see how it works...

I still get virtuoso-t crazy without using kopete nor krunner though :(

Regards


Damnshock, proud to be a member of KDE forums since 2008-Oct.
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
It works on trunk, so I'm not sure if it applies cleanly to branch:
http://lists.kde.org/?l=nepomuk&m=129448248620840&w=2


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
einar wrote:It works on trunk, so I'm not sure if it applies cleanly to branch:
http://lists.kde.org/?l=nepomuk&m=129448248620840&w=2


Nice, thanks a lot. In the meantime, I was trying to find a culprit but wasn't very successful. Once virtuoso-t went mad after starting skype (give it or take one second) even without running anything from kdepim or kopete. The second time it was crazy from logging in.

I will try the patch and let you guys know.

Btw, I should note that I was starting skype through krunner (with contacts disabled).
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
Did you also disable "Nepomuk Search" along with "Contacts"?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar
jirik
Registered Member
Posts
60
Karma
0
OS
einar wrote:Did you also disable "Nepomuk Search" along with "Contacts"?


:) You got me. Now I feel really stupid. I have disabled it now and will test it upon next boot.

Thanks again for your help.
User avatar
Damnshock
Registered Member
Posts
111
Karma
0
OS
No success here :(

Still crazy process!


Damnshock, proud to be a member of KDE forums since 2008-Oct.
User avatar
Naproxeno
Registered Member
Posts
28
Karma
0
OS
Same here.

I can't get virtuoso-t to behave.


Naproxeno, proud to be a member of KDE forums since 2008-Oct.
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
You could try asking your distribution to provide this patch:

http://lists.kde.org/?l=nepomuk&m=129448248620840&w=2

It fixes the CPU problem, but as a side effect on the first run it'll trigger a long conversion process.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
biasquez
Registered Member
Posts
34
Karma
0
OS
einar wrote:You could try asking your distribution to provide this patch:

http://lists.kde.org/?l=nepomuk&m=129448248620840&w=2

It fixes the CPU problem, but as a side effect on the first run it'll trigger a long conversion process.



it seems that natty with kdepim 4.6 beta 4 has this patch
User avatar
Naproxeno
Registered Member
Posts
28
Karma
0
OS
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?


Naproxeno, proud to be a member of KDE forums since 2008-Oct.
biasquez
Registered Member
Posts
34
Karma
0
OS
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?


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell