Window decoration and window don't look unified (sometimes) when shown by "Cover switch". This happens everytime on login. There is no such issue when I change the backend from OpenGL to XRender and then again to OpenGL. Reproducible: Always Steps to Reproduce: 1. Fresh login 2. Open a window 3. Alt+Tab - Cover switch Actual Results: Screenshot to follow Expected Results: Screenshot to follow
Created attachment 74297 [details] Initial incorrect screenshot
Created attachment 74298 [details] Second screenshot (After OpenGL -> XRender -> OpenGL)
Just found that just disabling and renabling desktop effects also corrects the problem. I'm using Intel graphics hardware/drivers (openSUSE 12.2)
You set the version information to 4.9.1. Is this correct? OpenSUSE 12.2 is not shipping 4.9 yet. If it is really 4.9 please run qdbus org.kde.kwin /KWin supportInformation once when the issue occurs and once when it is ok and attach the information here
Created attachment 74299 [details] Output Yes I'm on 4.9.1 (using repo http://download.opensuse.org/repositories/KDE:/Release:/49/openSUSE_12.2/) kwin -v Qt: 4.8.3 KDE Development Platform: 4.9.1 "release 561" KWin: 4.9.1 "release 561"
Created attachment 74300 [details] Output when the issue is present (previous attachment was for when the issue is not present; forgot to mention earlier)
There is not much we can do about it. It's with OpenGL quite normal that you see these lines (it is THE argument for client side window decorations). The fact that restarting the OpenGL compositor affects it, might be by pure chance and might be related to some internal state inside the driver. But it's nothing we can actually trigger. Overall it's more a CANTFIX from our side as it's a known OpenGL limitation.
That looks like an upstream bug, because kwin /is/ using GL_CLAMP_TO_EDGE ? (*the* one single error in gl usage responsible for this bug; so much that the nvidia blob had for years silently mapped the call and now still has a setting and an env for it ;-)
@Martin Isn't this bug #257566?
yeah it is *** This bug has been marked as a duplicate of bug 257566 ***