Solved Plasmashell runs at 100% since last upgrade

neal

neal

Since the recent upgrade of KDE to 6.6.2, plasmashell runs at 100% all the time.

I've tried reinstalling KDE and even running under Wayland, but to no avail.

I'm surprised that no one else has mentioned this problem, but I've been running KDE for quite some time with no problems (once I disabled baloo of course) and all that has changed is the upgrade to the new version so I can't imagine I'm alone with this problem.
 
neal said:
Since the recent upgrade of KDE to 6.6.2, plasmashell runs at 100% all the time.

I've tried reinstalling KDE and even running under Wayland, but to no avail.

I'm surprised that no one else has mentioned this problem, but I've been running KDE for quite some time with no problems (once I disabled baloo of course) and all that has changed is the upgrade to the new version so I can't imagine I'm alone with this problem.
Click to expand...
You're not alone indeed, it's a known bug; it's been discussed here, but probably is not much in evidence: https://forums.freebsd.org/threads/trying-to-run-kde-6-plasma-with-wayland.93951/page-31#post-748576.

This thread you started should help others find the solution more easely. :)
 
Faced this issue today after the upgrade to plasma version 6.6.3 on the quarterly channel. Thanks dshdsh for the "show seconds" workaround; the desktop was almost unusable with plasma running at 100% cpu.
 
dshdsh said:
Found it! In my case it was "Show seconds:" "Only in the tool-tip". I changed it to "Never" and plasmashell stopped eat CPU. Thanks.
Click to expand...
You are a savior. Worked for me too, kind of a bummer tho, since I love constantly seeing precise number of seconds on my second monitor's clock widget (don't ask why, I'm weird). Oh well, I guess that's why you shouldn't blindly update everything before going to bed just cause you're fixated on it lol.
 
  • Like
Reactions: drr
dshdsh said:
Found it! In my case it was "Show seconds:" "Only in the tool-tip". I changed it to "Never" and plasmashell stopped eat CPU. Thanks.
Click to expand...
Is that a bug with abnormally-high CPU use, or just that showing seconds is high CPU for some reason on Plasma?

Windows 11 has a toggle to show seconds in taskbar but also notes it increases power use; I figured it would interact with screen PSR (forcing refreshes each second), but wouldn't think that'd literally take extra processing power.
 
I can't get rid of it, right click on clock -> configure digital clock -> Show seconds is "Never". On 15, Xorg.

Edit : eventually it yielded, but not on the first DE restart
 
dshdsh said:
Found it! In my case it was "Show seconds:" "Only in the tool-tip". I changed it to "Never" and plasmashell stopped eat CPU. Thanks.
Click to expand...
It helped in my case as well - thanks a lot.
This annoying CPU usage by plasmashell started after the recent update, in which plasma was updated. It was very noticeable, as I have a NUC with a noisy vent, so 100% CPU is a real issue.
 
FreBSD 14.4-RELEASE-p1 with plasma6. I've set Digital Clock show seconds to never. plasmashell is still pegging 100% CPU

Thread 1 (LWP 100715 of process 1739):
#0 _fstatat () at _fstatat.S:4
#1 0x000000083f311c5c in ??? () at /usr/local/lib/qt6/libQt6Core.so.6
#2 0x000000083f318892 in ??? () at /usr/local/lib/qt6/libQt6Core.so.6
#3 0x000000083f24fade in QTimeZone::systemTimeZone() () at /usr/local/lib/qt6/l
ibQt6Core.so.6
 
Paul Floyd said:
FreBSD 14.4-RELEASE-p1 with plasma6. I've set Digital Clock show seconds to never. plasmashell is still pegging 100% CPU

Thread 1 (LWP 100715 of process 1739):
#0 _fstatat () at _fstatat.S:4
#1 0x000000083f311c5c in ??? () at /usr/local/lib/qt6/libQt6Core.so.6
#2 0x000000083f318892 in ??? () at /usr/local/lib/qt6/libQt6Core.so.6
#3 0x000000083f24fade in QTimeZone::systemTimeZone() () at /usr/local/lib/qt6/l
ibQt6Core.so.6
Click to expand...
It still takes some time to settle, in my experience about 30 seconds.
 
  • Like
Reactions: drr
The "show seconds to never" fix also worked for my desktop, thank you all.

There seems to be a separate issue somewhat related to this when locking (at least for me). When I lock my session, the kscreenlock_greet process jumps to 100% cpu usage. I tried to see if it was a similar issue with the clock functionality. However, disabling clock in the screen lock settings did not help. Has anyone else had this issue?
 
acesp said:
The "show seconds to never" fix also worked for my desktop, thank you all.

There seems to be a separate issue somewhat related to this when locking (at least for me). When I lock my session, the kscreenlock_greet process jumps to 100% cpu usage. I tried to see if it was a similar issue with the clock functionality. However, disabling clock in the screen lock settings did not help. Has anyone else had this issue?
Click to expand...
Paul Floyd said:
I also see kscreenlock_greet using 100% cpu on my 15.0-RELEASE laptop.
Click to expand...
Same here, seems that SDDM is affected by this bug too (and since it handles the locking of the screen too...).
 
You must log in or register to reply here.
Back
Top