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
99
100
101
102
103
104
105
106
107
|
<!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=%3C1309475446.31018.YahooMailNeo%40web161710.mail.bf1.yahoo.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006178.html">
<LINK REL="Next" HREF="006181.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?</H1>
<B>Radu-Cristian FOTESCU</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=%3C1309475446.31018.YahooMailNeo%40web161710.mail.bf1.yahoo.com%3E"
TITLE="[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?">beranger5ca at yahoo.ca
</A><BR>
<I>Fri Jul 1 01:10:46 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006178.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI>Next message: <A HREF="006181.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#6180">[ date ]</a>
<a href="thread.html#6180">[ thread ]</a>
<a href="subject.html#6180">[ subject ]</a>
<a href="author.html#6180">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i> The solution which worked most of the time for such issues in kde 4.6.xx was:
</I>><i> 1. open a terminal
</I>><i> 2. run killall plasma-desktop
</I>><i> 3. plasma-desktop
</I>><i>
</I>><i> the plasmoids and the desktop come back, and kded4 stops using that much CPU.
</I>><i>
</I>><i> Last time I looked what it was looking CPU at, it was caused by some run-away timer loop
</I>
><i> deep in kdelibs, but as those issues are quite random I haven't figured out what exactly causes this.
</I>
Евгений, thank you, but this is not a solution.
It is not a solution because, as soon as plasma-desktop is back, kded4 takes the same 55...75% CPU.
It is not a solution because, even if it were a temporary fix, it needed to be run after each and every login.
Now, I know my KDE is somewhat b0rken, because akonadiserver can't start -- but I could live just fine this way in KDE 4.6.3-4.6.4, if not even better than with it.
So I should report this as a bug, however I won't do it as long as I'm the only Cauldron user to experience it.
OTOH, let me tell you how to crash *any* KDE4 version (have to report it upstream, works on F15 too):
1. Folder View for the Desktop.
2. Click on a desktop icon, F2 (rename), select the text, right-click (as a reflex to find a menu with Copy);
3. plasma-desktop glorious crash.
Here's the KDE bug that was fixed by accident in KDE 4.6.90:
Upstream bug 235020, with duplicates 228036, 236800, 256257, 255393, 256993, 257591, 262912, 264287, 264664, 265064, 265823, 266245, 270591, 272198, 272662, 274792, 274135, 274659, 275301, 275906, 275906, 276020, 276261.
In short: KCharSelect crashes in some circumstances.
How to make KCharSelect crash on any version up to and including 4.6.4:
1. Open KCharSelect and make it have the minimum horizontal size (it should display 18 characters on a row; if it doesn't, keep it at this size nevertheless);
2. Select the "DejaVu Sans" or any other DejaVu typeface.
3. Keep "European Alphabets" in the first drop-down list.
4. In the second drop-down list, start to switch the code pages between the available ones, in order:
-- Basic Latin
-- Latin-1 Supplement
-- Latin Extended A
-- Latin Extended B
-- Latin Extended Additional
-- Latin Extended C
-- Latin Extended D
and so on.
5. It should have crashed by now. If not, keep switching back and forth between the code pages until it does!
The bug is actually triggered by unknown errors in some fonts (the DejaVu family being one of them).
It's funny to use KDE4 (I was a GNOME guy, that is, until GNOME Shell was announced). Except that kded4 is not funny.
Best regards,
R-C aka beranger
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006178.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI>Next message: <A HREF="006181.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#6180">[ date ]</a>
<a href="thread.html#6180">[ thread ]</a>
<a href="subject.html#6180">[ subject ]</a>
<a href="author.html#6180">[ 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>
|
