OK, so I just updated Tumbleweed to 20170615 (zypper dup --no-allow-vendor-*change) *and am now seeing a substantial increase in CPU utilisation attributed to plasmashell and kwin_X11.
Setting “cache: true” in “/usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml” as per comment #8 in the bug report ( https://bugs.kde.org/show_bug.cgi?id=381000#c8 ) has returned CPU utilisation to normal in my own case.
After using the machine normally, at the next image change an hour later the CPU utilisation went up to 70%+ and remained there. So, wrong, setting “cache: true” hasn’t solved it.
I’m having the same problem on tumbleweed.
Using static image as desktop background and “cache: true” didn’t help.
A temporary fix is to set xrender as kwin backend instead of opengl* and desktop becomes usable again.
It turns out that my trouble had nothing to do with plasma/kwin, it probably was a Mesa update that messed up prop. nvidia driver.
After I reinstaled nvidia everything came back to normal.
I hit 100% CPU on KDE 5.8 process “plasmashell” after upgrading to Leap 42.3 from 42.2 (and probably 42.1 before that, and who knows what before that). My system has a root partition and a home partition, so on each upgrade the home partition retained KDE plasma configuration and cache files, even though the system/root partition was wiped out with definitely the most recent upgrade, and probably upgrades before that.
Anyway, I tried several of the troubleshooting steps you see in the forums to stop KDE from pegging the CPU at 100%: deleting ‘animated’ widgets, disabling compositor, disabling search (baloo and tracker-miner) but it did not solve the problem
After troubleshooting by creating an entirely new user and logging in with that and using with no problem, I surmised that the true resolution was to delete all of the KDE, Plasma, and QT configuration files in the ~ or home directory. It was necessary to be aggressive and go beyond the usual suspects, deleted from /.config, /cache and /.local/share anything named “plasma”, “QT”, “tracker” and also things named “kde” more selectively, and also a cache having to do with fonts.
The deletions reset the desktop configuration but not much else, and so far so good, several hours of no problem from plasmashell. I also disabled search and compositor, but intend to re-enable them if there is no further problem.
Would be smart for the OpenSuse package managers to identify the specific older configuration file that is causing KDE 5.8 to peg the CPU with the upgrade, and the package maintainers should batch-delete it during the upgrade (with a warning), because KDE simply does not work out out-of-box in the standard OpenSuse upgrade procedure as a result of this issue.
This thread confuses me. It’s in the Tumbleweed stream, so any references to Leap surely are irrelevant? Also, i don’t understand any recent-post references to a Plasma version as old as 5.8.x… Tumbleweed is on 5.10.4 [since a couple of days], & 5.10.3 for several weeks before that… It was on 5.10.1 back in June. How is 5.8 relevant here?
BTW,
Anyone else have their cooling fans now going into overdrive?
–> no, never, nor any high cpu demand. As i write this, Tower fans running at normal background levels, cpu 3% - 11%, & temps:
Sorry, that’s impossible.
A package just cannot delete user config files on updates.
It would have to go through all users’ home directories, and /home might not even be mounted when packages are installed or it might be encrypted e.g.
Also, this is very likely highly specific to your system and/or configuration.
How should the packagers find out which file to delete?
Not to mention that this would definitely annoy some (most?) users.
KDE simply does work out-of-box in the standard openSUSE upgrade procedure, in general at least.
And please note that this thread is about a particular issue that’s caused by the wallpaper slideshow (though I don’t have that problem here either), and it is about Tumbleweed.
Especially as the problem apparently seems to be related to the upgrade to Qt 5.9. (Leap comes with 5.6)
Also, i don’t understand any recent-post references to a Plasma version as old as 5.8.x… Tumbleweed is on 5.10.4 [since a couple of days], & 5.10.3 for several weeks before that… It was on 5.10.1 back in June. How is 5.8 relevant here?
It is not relevant here at all.
But just to clarify: The latest Plasma version is 5.10.4.
Upstream KDE also still maintains the 5.8 branch too as LTS.
And Leap 42.3 does ship with the latest 5.8 LTS version, released in May (so it’s not really “old” in the chronological sense).
Yes, you did.
But my statement was (supposed to be):
Although the latest Plasma version is 5.10.4, upstream KDE also still maintains the 5.8 branch too as LTS (and that’s what is shipped in Leap 42.3).
this thread had seemed quite confusing / internally inconsistent.
Well, it happens that people post to threads that are not really related to their problem(s)…
