After updating my media-libs/mesa to 11.0.2 (from 10.x.y), I had issues with kwin[gles]. Most notably, the blur effect stopped working, resulting in a black region being drawn around each windows. A sample message given by "kwin --replace" is attached. I found out that the problem is known, see ${URL}. The issue is that by updating mesa, the advertised GLES version is now 3.0, with GLSL ES 3.00. And I was hitting the issue raised in the aforementioned bug. I tried the patch on the reviewboard: it removed some of the error, but it looks like kwin was not working better. See the second attachment. I switched to kde-base/kwin[opengl] and now it works perfectly. It looks like the solution is not straightforward: - Upstream does not want to fix it for KDE4 (cf bug and reviewboard) - It depends on the version of GLES being used. I don't know the version advertised with nouveau or amd-related drivers, so kwin[gles] + >=mesa-11 may still work for them. - If some desktop effects are disabled, it may look like it's working Would it be possible to at least put an ewarn in the ebuild if gles is enable that the user may experience trouble and should rather use opengl. I think I enabled gles to have wayland enabled as I wanted to play with it, even though this did not happened. Thanks!
Created attachment 413636 [details] output of kwin --replace
Created attachment 413638 [details] output of kwin --replace with the patch on the reviewboard
Created attachment 413640 [details] glxinfo with mesa 11
Please try mesa 11.0.3
Probably a duplicate of bug 562016 (known regression in mesa-11.0.2)
(In reply to Manuel Rüger from comment #4) > Please try mesa 11.0.3 Updating to mesa 11.0.3 makes kwin[gles] work again. But the blur plugin is still broken, see the attachement pure-kwin.txt. If I apply the patch given in $URL, it works fine (cf patched-kwin.txt).
Created attachment 414476 [details] kwin --replace without the patch
Created attachment 414478 [details] kwin --replace with the patch on the reviewboard
According to upstream bug report this should be fixed in 5.5.x which is in tree available.