On Thursday 5 September 2024 20:00:12 BST Peter Humphrey wrote: > On Thursday 5 September 2024 15:43:00 BST Iwrote: > > On Thursday 5 September 2024 13:47:29 BST I wrote: > > > ... Perhaps I should start recompiling things... > > > > After an emerge -e1 kwayland plasma-workspace and a reboot, kwin_wayland > > is > > down to 20-60% CPU and plasma_shell is barely visible in /top/. > > > > Much improved, but it still isn't right. > > It came back again, so I ran a complete -e, rebooted, recompiled the kernel > again and rebooted again. > > It's all back as it was - no CPU cycles left for anything else but wayland > and plasam-shell. > > How to debug this?
At a simple level you can check this file for any obvious problem: ~/.local/share/sddm/wayland-session.log Your symptom could be related to software rendering used by the kwin compositor, as opposed to OpenGL. Mesa with appropriate USE flags should provide what your graphics need. Have a look in kinfocenter, or run: qdbus6 org.kde.KWin /KWin supportInformation and check the section under Compositor, Compositor Type is not showing Xrender or software rendering. Beyond this I think you're into compiling stuff with debugging symbols and trying to understand where code fails: https://community.kde.org/KWin/Debugging
signature.asc
Description: This is a digitally signed message part.
