https://bugs.kde.org/show_bug.cgi?id=372015
--- Comment #12 from Sven Eden <sven.e...@gmx.de> --- Unfortunately this was a no go. And the "Backtrace" is highly illuminating: "Application: KWin (kwin_x11), signal: Aborted" That's it. Nothing more. No backtrace, nothing. (In reply to Martin Gräßlin from comment #11) > @Sven: the only possibility that KWin picks EGL without any config set to it > or env variable is that you compiled the Qt and KWin stack with OpenGL ES > instead of OpenGL. This is something we see quite often for Gentoo users. So there is a) the removal of the EGL/GLX choice, but b) a backdoor for EGL slithering back in without any control of the user. I'd call that an oversight that needs to be fixed? ;-) However, there was a time when GLES2 support was needed for EGL, which is needed for wayland. If that is no longer the case, we can eventually build everything without any OpenGL ES support? That would be so great! :-) (Honestly, GLES is a pain.) But as I see now, libsdl2-2.0.5 wants mesa with GLES2 support for it to be able to use wayland. Yes. It's configure script needs both video_opengl_egl and video_opengles_v2 to allow to enable video_wayland. ...what a pity. No wayland support for libsdl2 then. Everything else seems to have gotten rid of that ridiculous dependency. *yay*! (In reply to Martin Gräßlin from comment #11) > Concerning the Aurorae crash: no, nobody is working on it. While we see the > crash happens for many users, we devs have never been able to reproduce it. Well, I have no crash with mesa-12.0.4 and GLX. The whole damn thing is rock solid here. The only way for me to reproduce this is when "EGL" is chosen. (Which I just forced off anyway.) Buuuut maybe your hint about OpenGL ES 2 is the key to solving this. I am currently rebuilding everything that had GLES2 support without it. The fine thing about gentoo is, that we can easily try these things out, and even on a very fine grained scale. :-) -- You are receiving this mail because: You are watching all bug changes.
