Hi KDE team, If kde-frameworks/plasma is compiled with USE=wayland and USE=-egl, the Plasma Wayland session has all kinds of weird graphical artifacts that essentially make the session unusable compared to what it's like on Xorg. After looking around on the blog of the lead Wayland developer for KDE Plasma, it turns out that the upstream only supports EGL for Wayland while strongly recommending GLX for Xorg. Using EGL in Wayland still allows one to use OpenGL for the compositor, OpenGL ES 2 is not required. After re-compiling with USE=egl, USE=wayland, and USE=-gles2 set in /etc/portage/make.conf the problems with Plasma Wayland are gone and the legacy Xorg session is still usable. Quoting from Martin's blog: "A change which also got backported to a 5.7 bugfix release is the removal of the selection of GLX or EGL in the compositor settings. Unfortunately EGL is still not a good enough option on X11. Way too often we saw bug reports about rendering being broken and it was caused by using EGL. We decided that it doesn’t make sense to expose a config option which in most cases will result in the users systems being broken. So on X11 the default will stay GLX, while on Wayland the only option is EGL. Of course on X11 the option can still be set manually be editing the config file or by specifying the environment variable to pick EGL or to pick OpenGL ES 2." https://blog.martin-graesslin.com/blog/2016/08/opengl-changes-in-kwin-compositing/ http://blog.martin-graesslin.com/blog/2012/09/who-needs-glx-kwin-does-not/ Reproducible: Always
Thanks, I've dropped USE=egl instead and added the dependency +build switch under USE=wayland in commit c848a2355c8ede11b283cd40babf915c60700f2c
