On 15 October 2015 at 20:26, Andreas Müller <[email protected]> wrote:
> On Fri, Oct 9, 2015 at 2:20 PM, Jussi Kukkonen <[email protected]> > wrote: > > > > Recap of the situation as I understand it: > > * Gtk+3 works fine without any OpenGL, if GtkGLArea is not used > > * When GtkGLArea is used, Gtk+ uses libepoxy which is supposed > > dlopen the correct libraries as they are needed > I have several gtk3+ applications that stopped working. E.G > network-manager-applet has stopped working: running > nm-connection-editor fails with 'Couldn't open libGL.so.1'. Same for > parole. > I just realized this as well. Gdk initialization calls epoxy which calls exit() if libGL.so.1 is not there. This is clearly a major problem as it happens for all GTK+ applications, not just GL users. As an aside the reason this didn't come up before was that something seems to cache that initialization: If I run an application with libGL.so.1 in place once, I can then remove the library and run the application again successfully... Not sure what's going on there but it did hide the problem from me. A quick workaround is setting environment variable "GDK_GL=disabled". I'm looking at other possible fixes now. Jussi
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
