XCB 1.1 in ports -- assertion behaviour changed
tilman at crux.nu
Sun Nov 18 11:23:14 UTC 2007
I've put libxcb 1.1 in ports some days ago. In previous versions, the
CRUX port used to disable the xlib locking assertions. In 1.1, the XCB
developers added support for suppressing the assertions using the
environment variable LIBXCB_ALLOW_SLOPPY_LOCK.
So if you've got Xlib applications crashing with the locking assertion,
please set LIBXCB_ALLOW_SLOPPY_LOCK=1.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the CRUX