On Friday 03 September 2021, Roger Oberholtzer wrote:
On Fri, Sep 3, 2021 at 1:40 PM Philippe Andersson <pan@iba-group.com> wrote:
On 03/09/2021 09:48, Michael Hamilton wrote:
When something like that happens to me it's usually because compositing has been disabled due to some past glitch. If I re-enable it via Settings -> Display and Monitor -> Compositor, then all is well. This happens infrequently but I often fail to notice immediately, I've setup a login job that checks it:
---- snip --- #!/bin/bash #set -x
compositor_enabled=$(qdbus-qt5 org.kde.KWin /Compositor org.kde.kwin.Compositing.active)
if [ "$compositor_enabled" != "true" ] then notify-send -a "Check Compositor" -t 0 -i dialog-error.png 'Hardware -> Display and Monitor -> Compositor is disabled!' fi ---- snip --- Many thanks, Michael -- you nailed it!
The status on my system is true. I wonder where the transparency via the window title scroll went. Hmmm. Different topic.
I'm glad the suggestion worked. In respect to transparency control via the titlebar, I got curious... On TW Settings -> Window Management -> Window Behaviour -> Titlebar Actions - Mouse Wheel has a setting called "Change Opacity". If I set it, when I use the mouse wheel while over a titlebar, then the opacity of the window changes. I'm might try it for a while, I'm not convinced I have a use for it. I also noticed a titlebar action for double-click which will shade the window, I might find that more usefull. I'm going to try the xrender option too. After years of relative stability, on rare occasions google-chrome-beta manages to hard lock my nvidia based desktop. Switching off chrome's use of the GPU seems to reduce the occurrences to zero. Perhaps taking direct access to opengl away from KDE might help. I already switched to chrome non-beta, so I guess I won't know what, if anything, has made a difference (the reason I need the GPU enabled for chrome, is youtube will otherwise reduce the resolution or anything I watch). Michael