Registered Member
|
Hello,
Recently, I switched to using OpenSuse (currently version 12.2). I am now using KDE SC 4.10, but since KDE 4.9.x I have been unable to use nepomuk because activating it causes the virtuoso-t process to use all of the available RAM. Has this happened to anyone else? Can it be solved? Should a bug be filed against OpenSuse, Virtuoso, or maybe in the KDE bugtracker (against Nepomuk, maybe?)? I searched bugs.kde.org and the Novell bugzilla, but did not find anything relevant. Thanks in advance.
Last edited by Luther Blisset on Sat Feb 09, 2013 9:25 am, edited 1 time in total.
|
Registered Member
|
This issue is known for a long time. I get it, it works, I get it, it works...
So first, disable nepomuk for your email on kde system configuration. If you don't use it for your emails, there's a lot of reading : To debug in opensuse : http://kdeatopensuse.wordpress.com/2011 ... cpu-usage/ Some solutions : https://bbs.archlinux.org/viewtopic.php?id=134567 https://bbs.archlinux.org/viewtopic.php?id=112499 kde bug : https://bugs.kde.org/show_bug.cgi?id=289932 I don't search about recent threads in google, there are threads I use to solve problem when they occur. |
Administrator
|
How much RAM does your system have, is file indexing enabled, and what level of "memory usage" is specified in the "Advanced Settings" section of "Desktop Search" in System Settings?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Those are for CPU usage, not RAM usage.
My system has 4 GB of RAM, file indexing is enabled, and virtuoso-t is restricted to use 50 MB (which IIRC is the default setting). |
Administrator
|
Please make sure you have installed all available updates, and then try to reproduce under a new user, just to confirm no old configurations are causing this issue.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I have installed all available updates. I have been unable to reproduce the problem under a new user. I'll try nuking any old configs (I take daily backups of /home/myUser, so I don't think I'll permanently damage anything ) and see if it helps. EDIT: Problem solved. Thanks for your help, bcooksley. |
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]