Re: [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
Re: [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
- Subject: Re: [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
- From: Jeremy Huddleston Sequoia <email@hidden>
- Date: Sun, 29 Mar 2015 14:15:20 -0700
> On Mar 29, 2015, at 14:02, René J.V. Bertin <email@hidden> wrote:
>
> On Sunday March 29 2015 11:57:16 Jeremy Huddleston Sequoia wrote:
>
>>> The OpenGL examples run on a local X server, despite the fact that the xcb plugin links to both the X11 GL libraries and {OpenGL,AGL}.framework .
>>
>> Yeah, you should drop those other links. Hopefully the libGL link is at least first. Most of the gl* function calls in the mesa libGL just forward on to OpenGL.framework, but there are a few that don't.
>
> I can try (once more) to see if it changes anything if I drop those links, but the list currently seems to have an appropriate order:
You can run 'nm -m /opt/local/share/qt5/plugins/platforms/libqxcb.dylib | grep OpenGL' to see if there is anything actually using the OpenGL.framework link. However, this linking is certainly not the source of your problems.
<snip/>
> But that would just be the xcb plugin. The host applications will still be linked against {OpenGL,AGL}.framework, at least as long as I just build the xcb platform plugin as an alternative for a Qt install that uses Cocoa by (and as the supported) default.
Then that's a bug in how the application is linking and would need to be fixed there as well.
>> BTW, assuming you're using XQuartz, we provide the dSYMS. Eg:
>> http://xquartz-dl.macosforge.org/SL/XQuartz-2.7.8_rc1.dSYMS.tar.bz2
>
> That's good to know, thanks.
>
>> I suspect this is http://xquartz.macosforge.org/trac/ticket/420
>
> That does seem relevant indeed.
>
>> No, it's almost certainly the XQuartz-specific GLX bits in mesa that haven't had much attention in 6+ years.
>
> The fact that there's a BadValue error is unlikely to be Qt's doing, nor the deadlock in XLockDisplay. But is there nothing Qt applications could or should do to handle the window-close event in such a way that the issue is avoided?
I doubt it. They're just victims of the rather bitrotted GLX codebase for XQuartz.
>> Note that we need a few patches to get things working:
>> http://trac.macports.org/browser/trunk/dports/x11/mesa/files
>
> I'll see if installing the latest port:mesa changes anything.
I don't expect it would.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden