On 11/10/2017 08:48 PM, Robert Kudyba wrote: > Does this help, from gdb /usr/bin/mate-session > /var/lib/systemd/coredump/core.mate-session.1000.d7ae5cd424f743dcbbdad920fbc58b7b.2731.1510340293000000 > > > [...] > Reading symbols from /usr/bin/mate-session...Reading symbols from > /usr/lib/debug/usr/bin/mate-session.debug...done. > done. > [New LWP 2731] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > Core was generated by `mate-session'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f3ffb453627 in XGetXCBConnection (dpy=dpy@entry=0x55e55b465000) at > x11_xcb.c:9 > 9 return dpy->xcb->connection;
Not really, I fear. I'm unable to reproduce this. Have tested both with the current X2Go nx-libs release builds and Mike#2's copr repo for the arctica version. In both cases MATE starts up without segfaulting in xcb. However, for some reason I even have direct rendering available in the session. Merely through MESA's software renderer, but still working fine. I can even disable the GLX extension. In this case, direct and indirect rendering are not available, but MATE is still starting up correctly. People have suggested that libgles1/2 must be available on the system, so what about: rpm -qa | grep mesa-libGLES Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
