On 10/27/07, Luke Hoersten <[EMAIL PROTECTED]> wrote: > I don't think it's just the JDK. Many people trying to use the JRE are > having the same problem ...
Yes, this is a generic Java issue. The JRE is a subset of the JDK that contains almost all the same code. The distinction is too troublesome for normal discussion. > Does anyone know of a workaround or patch for this problem? Sure. You can turn off Xinerama support in your X server, or as Josh Triplett documented in June, you can effectively disable Xinerama support in Java: https://bugs.freedesktop.org/show_bug.cgi?id=9336#c15 Upstream libxcb also now has a variant of the Novell sloppy lock patch, so that you can set an environment variable to disable the asserts when you run broken applications, like Java before JDK7 beta 22. Furthermore, experimental packages of JDK7 are available for Ubuntu Gutsy and are expected to work with Debian as well. http://lists.debian.org/debian-java/2007/08/msg00028.html > Here's a list of some other bug reports: All the bug reports you listed are already fixed, both upstream and in Debian, Gentoo, and I assume in Ubuntu and elsewhere. None of them are relevant to the Java issue. Why do you bring them up? -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs