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/006336.html | 112 +++++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006336.html (limited to 'zarb-ml/mageia-dev/2011-July/006336.html') diff --git a/zarb-ml/mageia-dev/2011-July/006336.html b/zarb-ml/mageia-dev/2011-July/006336.html new file mode 100644 index 000000000..7101449bb --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006336.html @@ -0,0 +1,112 @@ + + + + [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?

+ Radu-Cristian FOTESCU + beranger5ca at yahoo.ca +
+ Mon Jul 4 14:47:53 CEST 2011 +

+
+ +
But removing ntrack does not fix anything! (CPU 100%) Maybe removing libtrack0? 
+
+R-C (sorry 4 top-posting, I'm on Nokia)
+
+On Mon Jul 4th, 2011 3:26 PM EEST John Balcaen wrote:
+
+>2011/7/4 Radu-Cristian FOTESCU <beranger5ca at yahoo.ca>:
+>>
+>>
+>>> you can reproduce it by removing with --no-deps ntrack & restart your
+>>> kde session
+>>
+>> You mean one could have been running "kded4 --no-deps ntrack" and experience no CPU issues even w/o these updates?!
+>> Geez, how would a regular user know that "--no-deps ntrack" was a valid parameter?
+>it was a rpm command aka  remove the ntrack package with --nodeps aka
+>rpm -e --nodeps ntrack
+>& not running kded4 whith thoses argument.
+>
+>
+>
+>-- 
+>Balcaen John
+>Jabber-id: mikala at jabber.littleboboy.net
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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