The (first) error message is expected when LIBXCB_ALLOW_SLOPPY_LOCK=1 is enabled.
As long as your app isn't crashing, you can safely ignore the error, since your app doesn't mix xlib and xcb.
The long term solution should be "socket handoff," but I don't think that will hit hardy: http://lists.freedesktop.org/archives/xcb/2008-March/003347.html
The (first) error message is expected when LIBXCB_ ALLOW_SLOPPY_ LOCK=1 is enabled.
As long as your app isn't crashing, you can safely ignore the error, since your app doesn't mix xlib and xcb.
The long term solution should be "socket handoff," but I don't think that will hit hardy: http:// lists.freedeskt op.org/ archives/ xcb/2008- March/003347. html