From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-July/006301.html | 76 ++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006301.html (limited to 'zarb-ml/mageia-dev/2011-July/006301.html') diff --git a/zarb-ml/mageia-dev/2011-July/006301.html b/zarb-ml/mageia-dev/2011-July/006301.html new file mode 100644 index 000000000..85e850ac5 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006301.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90? + + + + + + + + + +

[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?

+ Renaud MICHEL + r.h.michel+mageia at gmail.com +
+ Sun Jul 3 23:05:00 CEST 2011 +

+
+ +
On dimanche 03 juillet 2011 at 21:40, Radu-Cristian FOTESCU wrote :
+> I have used "qdbus org.kde.kded /kded unloadModule" to unload, one by
+> one, each and every module, until "qdbus org.kde.kded /kded
+> loadedModules" listed nothing.
+> 
+> So even with no loaded module, kded4 is taking too much CPU.
+
+You should do it the other way, because if one of the modules entered en 
+infinite loop (which is likely if you have one core at 100% with no IO) it 
+is likely that it won't unload properly. It may not be in kded's list 
+anymore, but still running loose in his thread.
+
+So you should disable all kded modules (from systemsettings), then log off 
+(or even restart to be sure no process is left running) then log back on. If 
+you still get high CPU from kded then ths problem is in kded itself, if not 
+you can start loading the modules one by one (waiting long enough between 
+each) to identify which one will start eating the CPU.
+
+-- 
+Renaud Michel
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1