summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006198.html
blob: 63fbc4889aefb7d8ee27eee70471576fe8cc81f3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Anybody%20having%20high%20CPU%20by%20kded4%20after%20upgrading%0A%09to%204.6.90%3F&In-Reply-To=%3C201107010828.25298.maarten.vanraes%40gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006196.html">
   <LINK REL="Next"  HREF="006200.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?</H1>
    <B>Maarten Vanraes</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Anybody%20having%20high%20CPU%20by%20kded4%20after%20upgrading%0A%09to%204.6.90%3F&In-Reply-To=%3C201107010828.25298.maarten.vanraes%40gmail.com%3E"
       TITLE="[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?">maarten.vanraes at gmail.com
       </A><BR>
    <I>Fri Jul  1 08:28:25 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006196.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?
</A></li>
        <LI>Next message: <A HREF="006200.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6198">[ date ]</a>
              <a href="thread.html#6198">[ thread ]</a>
              <a href="subject.html#6198">[ subject ]</a>
              <a href="author.html#6198">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Op vrijdag 01 juli 2011 07:40:24 schreef Radu-Cristian FOTESCU:
&gt;<i> I was trying to investigate the kded4 high CPU load, and I started to
</I>&gt;<i> investigate some upstream reports, even if not necessarily reported for
</I>&gt;<i> 4.6.90.
</I>&gt;<i> 
</I>&gt;<i> Some such reports were related to ntrack, e.g. <A HREF="http://bugs.kde.org/268038">http://bugs.kde.org/268038</A>
</I>&gt;<i> 
</I>&gt;<i> What the heck is ntrack and why do we need it? (The official description
</I>&gt;<i> tells me exactly nothing).
</I>&gt;<i> 
</I>&gt;<i> There is *no* ntrack in either of Mandriva or Fedora -- it's actually
</I>&gt;<i> likely to be an Ubuntu project; either way, it's definitely *not* part of
</I>&gt;<i> the KDE4 project, as it's hosted on <A HREF="https://launchpad.net/ntrack">https://launchpad.net/ntrack</A>
</I>&gt;<i> 
</I>&gt;<i> Then why the heck removing libntrack0 wants to remove *all* the KDE???
</I>&gt;<i> 
</I>&gt;<i> Is Mageia becoming Kubuntu?
</I>&gt;<i> 
</I>&gt;<i> All these excessive dependencies are making me sick. Everything depends on
</I>&gt;<i> everything. Is dynamic loading of libraries, with dynamically getting
</I>&gt;<i> pointers to functions and using them or not, depending on availability, a
</I>&gt;<i> mechanism that only works in Windows?
</I>&gt;<i> 
</I>&gt;<i> Then, you'll excuse me, for the fist time in 9 days, I'll reboot into XP
</I>&gt;<i> SP3.
</I>&gt;<i> 
</I>&gt;<i> And I'm doing that because, after having rebooted in F15, their plasma
</I>&gt;<i> (4.6.3) crashed on me for 3 times in 5 minutes. This is unbearable.
</I>&gt;<i> 
</I>&gt;<i> Pissed off,
</I>&gt;<i> R-C aka beranger
</I>
dude, it kind of pisses me off what i read here...

you're using &quot;cauldron&quot;; it's nice that you find these bugs so they can be 
fixed, but i mean... it's &quot;cauldron&quot;, imho you can't expect s stable state in 
our &quot;development version&quot;... so please, do what everyone else does in 
cauldron:
 - use another DE if the current one is unworkable.

afaik ntrack, if that is a problem, why don't you try and recompile KDE 
locally without ntrack? see if it improves stuff?
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006196.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?
</A></li>
	<LI>Next message: <A HREF="006200.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading	to 4.6.90?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6198">[ date ]</a>
              <a href="thread.html#6198">[ thread ]</a>
              <a href="subject.html#6198">[ subject ]</a>
              <a href="author.html#6198">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>