The plasmashell devil is not defeated - fluff is more important.

English Applications
1

The KDE’s plasmashell bug, leading to 100% CPU load, is still there in Leap 42.2 Beta. I installed the Leap, and, with almost no useful load, the CPU usage by the devil increased from 6% to 100% in a day. Memory usage didn’t increase, staying at 9%. This is an unusual, very persistent bug.

The KDE team has no clue, after years. A user writes on the bugs.kde.org:

“this bug (or its many variants) has been ongoing since 2012 (im currently on plasma 5.7.0). It is a big problem for the use of laptops on battery. I cannot understand a design descision which prioritises “graphical fluff” over system functionality and the sanity and time of your users.”

As of August 2016, they are considering ways to create a controllable setup to investigate the bug; see Post 70 at https://bugs.kde.org/show_bug.cgi?id=356479

From here and there, I gathered that there are about thirteen people in KDE’s plasma team. The turnaround is very high, perhaps 30% per year, maybe because many are interns and students.

Now, I wonder whether it is possible to run KDE in Leap without starting the plasmashell devil, perhaps by using the KDE of opensuse 13.2 or 13.1 in Leap? Maybe opensuse can assemble a distribution called “plasmashell-free Leap”?

SuSE is among sponsors/patrons of KDE. I wonder how SuSE Linux is dealing with the devil. Other Linuxes suffer from it as well.

2

Hi
Why not run perf as root user to see what it actually is, keep an eye on usage and at times run the following as root user?


perf record -F 250 -g -a sleep 10
perf report

Once you have one report, rename perf.data to something usefull and then when it creeps up more run again etc…

3

I looked at perf output, without much understanding. The main consumers of CPU are plasmashell and X-related utilities. The main shared objects are Qt libraries and libc. Nothing unusual, as far as I can see, it is the summed up CPU usage that is high. I also made an attempt to install KDE4 instead of plasma5, failed.

4

not the only one with terminal and cpu issues – leap 42.1
also it is NOT all the time

i close out a terminal and it may or may not cause one of the CPU’s to go to 100%
and sometimes the bug report screen comes up , sometimes not

i keep " system load viewer " in the toolbar and use <ctrl>+<esc> a lot