I updated from Plasma 6.5 to 6.6 yesterday and the system became sluggish (lag between mouse click and actions) when interacting with certain applications, e.g., system settings, lock screen (but not initial login screen), spectacle.
When interacting with them I see a significantly higher memory consumption and CPU spikes. Using a browser, the terminal or even an electron app shows no such issues though.
I didn’t see anything relevant in journalctl /usr/bin/plasmashell, so I tried to revert from Plasma 6.6 to 6.5 using eos-shifttime. After the reboot, the issues were gone. When I tried upgrading to Plasma 6.6 (pacman -S plasma) from that state and rebooting, the issues were back.
I’m unsure of what the actual issue is or how to debug this properly. Any ideas are welcome!
Partial updates are not supported by Arch based systems because it may/will lead to problems.
That’s why pacman with -Syu is sensible, especially if the system is in the state of partial updates.
The system was fully updated when I had these issues. The reverts and partial upgrades were just to try to isolate what component of the full upgrade was responsible.
Returning the system to the fully upgraded status (pacman -Syu) shows the issues I mentioned at the start of the thread.
Digging a bit further in the logs, I did find some messages that pop up when interactions are very slow, namely:
systemsettings[3774]: warning: queue 0x5593c3775600 destroyed while proxies still attached:
systemsettings[3774]: wl_display#1 still attached
As the original poster stated, there appears to be a memory issue within the Plasma 6.6 update. I have reverted back to 6.5 and will wait for someone to discover why it is happening.
Using two browsers open with many tabs present, my computer locks up and stops responding to mouse clicks. I can move the cursor, I cannot click to perform any function without rebooting.
Hi, sorry for entering this discussion despite not being an EndeavourOS user. I have upgraded to Plasma 6.6 in the recent days on my Fedora 43 Laptop and I noticed the same various lags after the Plasma 6.6 update, limited to the desktop and not apps such as the Google Chrome browser. I am also encountering the same difference in the usability between Plasma 6.5 and 6.6 on the Arch installation I have on a external drive but I don’t have rollbacks enabled on that system so I cannot confirm the issue is there 100% but undoubtedly looks more laggy with 6.6 also on Arch. So this seems more a Plasma upstream issue than a Arch/EndeavourOS one.
Hey Fede, good to have you with us. It may well be a Plasmashell memory leak, although it’s not been widely reported. Can you provide a little bit more info on your system?
Thanks, - there’s nothing obvious in your hardware specs or versioning that stands out. The first .x.1 patch is out this Tuesday for Plasma, if you can, hold out a few days, if you’re seeing the same issues in X11 as Wayland, it’s absolutely upstream.
Hi, I’ve updated to 6.6.1 but the issue seem unfixed. I wanted to give a try to KDE Neon to see if the issue persists also there but unfortunately it ships Kernel 6.17 or 6.8 which both don’t work quite well on my laptop. Also, after booting Neon with some kernel command line shenanigans KDE Login screen crashed when entering password (which is, btw, identical to what happens on Kubuntu….). I know my setup is very hostile to the Linux environment but still KDE 6.5 seemed to be way more fluent and after 6.6 update there is some minor yet noticeable stuttering.
Edit: I also tried creating a new user to see if it was caused by some config file updated from 6.5 to 6.6 but the issue was present also there.
I have updated to the latest Plasma 6.6.1 from 6.5.5 and I also face some slow system. Shutdown button appears and disappears. Some apps which depended on Wayland also stopped reporting proper gpu vendor and now loads using Softpipe (they used to render with OpenGL or LLMVpipe = Vulkan). But the only thing that I downgraded that made my system go back to previous state was KWin, the rest of Plasma components seems to not be the cause.