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/006241.html | 70 ++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006241.html (limited to 'zarb-ml/mageia-dev/2011-July/006241.html') diff --git a/zarb-ml/mageia-dev/2011-July/006241.html b/zarb-ml/mageia-dev/2011-July/006241.html new file mode 100644 index 000000000..3b330197c --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006241.html @@ -0,0 +1,70 @@ + + + + [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 +
+ Fri Jul 1 17:57:48 CEST 2011 +

+
+ +
+
+> ntrack is supposed to provide more information regarding connection/route 
+> change for desktop applications & such so we'll probably see 
+> applications or developpers used it later. If we can provide by default 
+> an environnement so developers can use it (aka no need to 
+> recompile/add 'x' br) if it's not a burden for end users why not providing it ?
+
+Thank you. It makes sense. However, it's very frustrating that the upstream doesn't bother to document what's new in such a release, being it an RC.
+They didn't even bother to list the most important bugs that are fixed (although I also suspect some bugs vanished as a side effect of some changes).
+
+Now, it's tough to determine what exactly is making kded4 to eat the CPU. As I'm having a single core, I'm burned. At the same time, minor changes that are actually small improvements make me want to stay with 4.6.90, not to revert to 4.6.4....
+
+R-C
+
+ + + +
+

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