> Hi, > > I know how Solaris has the binary back compatibility > thing to keep up > with so xcb can not be integrated right away. One > such bug that was > shown to me was: > http://bugs.sun.com/view_bug.do?bug_id=6532373 > Which I believe I have a workaround in xcb so that > the assertion is > not triggered when a xcb_xlib_unlock is incurred. > > Submitted By: Dan Nicholson <dnicholson AT > linuxfromscratch DOT org> > Date: 2007-07-08 > Initial Package Version: 1.0 > Upstream Status: Will not apply. > Origin: OpenSuSE > > ttp://download.opensuse.org/distribution/SL-OSS-factor > y/inst-source/suse/src/xorg-x11-libxcb-7.2-33.src.rpm > Description: This is a workaround for X11 > applications which have locking bugs > that will trigger assertions when libxcb is used. > An environment variable, > LIBXCB_ALLOW_SLOPPY_LOCK, can be set to skip the > check that the display lock > has been set correctly. This will not be merged > upstream as the XCB > developers have decided to be strict in exposing the > bugs so they are fixed > in the appropriate location.
I'm not clear on something. Would someone running an older JRE need to set LIBXCB_ALLOW_SLOPPY_LOCK. If you're trying to get it accepted, perhaps it should be enabled, and you manually have to unable it? -- This message posted from opensolaris.org
