drbabbles, A better workaround is to add a line "LIBXCB_ALLOW_SLOPPY_LOCK=1" to /etc/environment.
Regarding, your first comment, we can have our cake and eat it too. Just because we don't gratuitously crash applications doesn't mean we can't fix the underlying problems. A lot of extensions were affected by this. This means that whenever someone wants to use an application that includes statically linked older extension libraries, there's a good chance that it's gonna crash. That's completely absurd considering that the application will almost certainly work just fine. Fixing this issue is completely trivial and has probably been done already if the status of the bug is any indication. -- 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
