Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Wednesday February 20, 2008
11:04 AM

Java + X (xcb) bug workaround

[ #35704 ]

On Fedora 8, and probably several other operating systems, if you attempt to run a Java GUI application (specifically anything that uses AWT, and Swing uses AWT, so this is just about everything), you'll encounter the following error:

java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

This is due to a bug in xcb, although apparently the xcb developers initially felt it was not really their problem because it occurs when code (in this case, the JDK) is compiled on a machine which lacks a particular library and is executed on a machine which has that library. JDK 1.7 should include a workaround. In the meantime, the solution is to upgrade the libxcb package. libxcb 1.0-3.fc8 is known to exhibit the problem, 1.0-4.fc8 is known to be clean.

Update: 2008-07-31: libxcb-1.1-1.fc8.i386.rpm has been released which appears to bring this problem back. If possible, fix by setting environment variable LIBXCB_ALLOW_SLOPPY_LOCK to a value of 1. If you really want libxcb-1.0-4.fc8.i386.rpm, I have it, thanks to the help of Mr. Muskrat, and I do not intend to be turning loose of it any time soon. Post here or email me and I will happily provide it to you.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.