On Thu, Oct 15, 2015 at 9:42 PM, Burton, Ross <[email protected]> wrote: > On 15 October 2015 at 18:26, Andreas Müller <[email protected]> > wrote: > >> 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 grepped network-manager-applet: there is not GtkGL or GdkGL found in >> the sources (ok - it could be the dependencies). I still get the >> feeling something goes wrong with libepoxy. And I am quite sure that >> I've seen both (nm-applet/parole) running with gtk3 requiring >> libepoxy... >> > > That's not good, sounds like a bug in GTK+3 - it shouldn't be initialising > the GL code. > > The only bit of source that includes epoxy is gtkglarea.c. libepoxy only > looks up libGL.so.1 when it's invoked. That makes it even more mysterious... > > What's the exact message you get, and bonus points if you can attach a gdb > with debug symbols to get a backtrace. Maybe something like Glade is > instantiating every class? > I moved this thread to core - I sent to wrong list - sorry
Error messages are [operator@raspberrypi2 ~]$ nm-connection-editor Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory [operator@raspberrypi2 ~]$ parole Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory Yes gdb is what I try next. Andreas -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
