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 -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
