If I understand the original Debian thread correctly, this arises when someone writes sloppy code, no? Sloppy code should be fixed, instead of allowing broken behavior in the libraries...IMHO. Still, the closed- source java annoys me in that only Sun can fix the problem.
Is a fix forthcoming in libxcb, or do we wait for broken packages (Java most notably) to be updated? If no fix is in the pipeline, what is the temporary workaround? Just export and run java apps from the CLI every time? -- 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
