Created attachment 547736 [details] emerge --info output Hi, everyone, currently i am developing OPENGL application on gentoo minimal 4.14.65 kernel and amd64. I an facing issue related to opengl EGL content creation. If any can help this bug. it would be great. i am putting my logs here. This application works perfectly in gentoo 4.9.95 kernel version. But after updating kernel version i got this error in my application and also dkms packages. Thanks you. [2018-09-20 07:23:16.588] [opengl] [info] using card: /dev/dri/card0. [2018-09-20 07:23:16.592] [opengl] [info] ignoring unused connector 42. [2018-09-20 07:23:16.626] [opengl] [info] ignoring unused connector 44. [2018-09-20 07:23:16.752] [opengl] [info] %-------- Configuring EGL context settings -------- % [2018-09-20 07:23:16.755] [opengl] [info] EGL major/minor: 1.5. [2018-09-20 07:23:16.758] [opengl] [info] EGL Version: (1.5 (DRI2)). [2018-09-20 07:23:16.760] [opengl] [info] EGL Vendor: (Mesa Project). [2018-09-20 07:23:16.764] [hyperflow] [error] [EGL]: Renderer failed to init!!! cannot create EGL context this is my code auto gl_logger = spd::get("opengl"); gl_logger->info("{:^30}", "%-------- Configuring EGL context settings -------- %"); gl_logger->info("EGL major/minor: {0}.{1}.", major, minor); gl_logger->info("EGL Version: ({0}).", eglQueryString(this->display, EGL_VERSION)); gl_logger->info("EGL Vendor: ({0}).", eglQueryString(this->display, EGL_VENDOR)); gl_logger->debug("EGL extensions: [ {0} ].", eglQueryString(this->display, EGL_EXTENSIONS)); if (!eglBindAPI(EGL_OPENGL_API)) throw EGLException("cannot bind OpenGL API"); b = eglChooseConfig(this->display, conf_att, &this->config, 1, &n); if (!b || n != 1) throw EGLException("cannot find suitable EGL config"); this->context = eglCreateContext(this->display, this->config, EGL_NO_CONTEXT, ctx_att); if (!this->context) throw EGLException("cannot create EGL context");
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/