Java problem on fedora release 8 - test 3

[RVF16]

Hallo to all.

While testing Fedora 8 Test 3, i found this problem when trying to run some java apps :

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

After Googling it i found a thread where someone pointed the finger to libx11 updates.

So i installed the fc7 libX11-1.0.3-8.fc7.i386.rpm and libX11-devel-1.0.3-8.fc7.i386.rpm with the following command :
rpm -ihv --force libX11-1.0.3-8.fc7.i386.rpm libX11-devel-1.0.3-8.fc7.i386.rpm
(you can find them by fc7 search in http://rpm.pbone.net/index.php3/stat/2/simple/2)

and then removed the problematic version (libX11-1.1.3-4.fc8.i386.rpm and libX11-devel-1.1.3-4.fc8.i386.rpm) via SMART package manager.
It worked so try it out until an update comes out with this resolved.

Regards.

[leigh123linux]

Originally Posted by RVF16

Hallo to all.

While testing Fedora 8 Test 3, i found this problem when trying to run some java apps :

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

After Googling it i found a thread where someone pointed the finger to libx11 updates.

So i installed the fc7 libX11-1.0.3-8.fc7.i386.rpm and libX11-devel-1.0.3-8.fc7.i386.rpm with the following command :
rpm -ihv --force libX11-1.0.3-8.fc7.i386.rpm libX11-devel-1.0.3-8.fc7.i386.rpm
(you can find them by fc7 search in http://rpm.pbone.net/index.php3/stat/2/simple/2)

and then removed the problematic version (libX11-1.1.3-4.fc8.i386.rpm and libX11-devel-1.1.3-4.fc8.i386.rpm) via SMART package manager.
It worked so try it out until an update comes out with this resolved.

Regards.

Have you reported it to Java as it is a fault with there rpm or bin not being compiled against the new version libX11 !!

[RVF16]

I don't know where to report this cause as far as i understood reading another relevant thread one points own finger to the other.
Java (1.6.0_03) does work great with previous libX11 so probably its libX11 faulty.

And here is another one regarding Firestarter firewall :
After running it if you dare to click the "Active Connections" label it will crash after a while.
It is described as "***MEMORY-ERROR***: firestarter[3290]: GSlice: assertion failed: sinfo->n_allocated > 0"
Still searching for a solution to this one.

[leigh123linux]

Originally Posted by RVF16

I don't know where to report this cause as far as i understood reading another relevant thread one points own finger to the other.
Java (1.6.0_03) does work great with previous libX11 so probably its libX11 faulty.

And here is another one regarding Firestarter firewall :
After running it if you dare to click the "Active Connections" label it will crash after a while.
It is described as "***MEMORY-ERROR***: firestarter[3290]: GSlice: assertion failed: sinfo->n_allocated > 0"
Still searching for a solution to this one.

F8 is cutting edge and uses a new version libX11 that java is incompatible with ., as for the firewall issue have you tried the new firewall frontend that is included as standard as it is better than Firestarter.

[RVF16]

I have messed a bit with the new fedora firewall and it looks great butl the reason i still want firestarter on my desktop is the display of active connections.
Many, switching from Windows to Linux, have expressed the need for a NetLimiter style application and firestarter is a step towards that though its early days for an adequate app.

Now regarding Java i got your point about the incompatibility with the latest libX11. Where do i report this, in http://bugs.sun.com/? The only thing i have is this message "java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed." and i got confused with their bug report form.

[a_user]

Hello,
I have found the following post on one of the Sun's forums. It did work for me. All yo have to to is to change the installation path in the trick.
***********(COPIED)***
Submitted On 01-JUN-2007

I worked with jcristau and christoph4 via IRC on #debian-x, and we managed to
track down the problem with broken locking in Sun Java 1.5 and 1.6. It only
occurs if Java finds the Xinerama extension, at which point it does something
broken with locking and triggers the assertion. If Java never finds the
Xinerama extension, it doesn't trigger the assertion for broken locking.

The following workarounds address this problem:

For sun-java5-bin:
sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/i386/xawt/libmawt.so

For sun-java6-bin:
sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/xawt/libmawt.so

The same fix (applied to the appropriate file) might work for other
proprietary JDKs.

- Josh Triplett
************************************************** *********

All the credit goes to Josh Triplett, I just had the same problem you had and found this on the web.

Best.

a_user

[pressh]

Great! Thanks for the workaround, it works like a charm on fc8 with java6.

Of course I had to put in the appropriate path to libmawt.so, so for the move novice users on the forum, for the workaround above, do as root in the terminal

sed -i 's/XINERAMA/FAKEEXTN/g' $YOURPATHTOJRE/lib/i386/xawt/libmawt.so

where $YOURPATHTOJRE should be changed to where you installed java, probably something like /opt/jre1.6 (well you know where it is as you installed it yourself).

All credits of course to J.T.

[aljo666]

Does anyone have the solution to this for the 64bit version?

[myname74119]

Does anyone have the solution to this for the 64bit version?

[rweed]

This works for the 64-bit version, too (so far!).

[giulix]

Thanks, a_user. It's been driving me mad for the last 2 days...

[jdeslip]

even after applying the sed command I still get this error when trying to run matlab

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

I installed the jre-6u3-linux-i586-rpm.bin to the default /usr/java location and then did:

sed -i 's/XINERAMA/FAKEEXTN/g' /usr/java/jre1.6.0_03/lib/i386/xawt/libmawt.so

but the matlab problem still persists. It also persists if change to using the icedtea version by running alternatives ...

Any help?

[jdeslip]

ok, I figured it out - my (somewhat ancient) version of matlab came with its own java. So I needed to do

sed -i 's/XINERAMA/FAKEEXTN/g' /usr/local/matlab/sys/java/jre/glnx86/jre1.5.0/lib/i386/xawt/libmawt.so

[evans]

jdeslip,

thanks for the tip about the java in the the matlab installation directory. I have now ran the sed command twice:


sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-1.7.0-icedtea-1.7.0.0/jre/lib/i386/xawt/libmawt.so
sed -i 's/XINERAMA/FAKEEXTN/g' /usr/local/matlab704/sys/java/jre/glnx86/jre1.5.0/lib/i386/xawt/libmawt.so

I still get the same error with matlab though? are there other libmawt.so? there's one under my mathematica install directory, should I do that one too? why?

[evans]

OK, I should have played a bit more: doing

sed -i 's/XINERAMA/FAKEEXTN/g' /usr/local/matlab704/sys/java/jre/glnx86/jre1.5.0/lib/i386/motif21/libmawt.so

did it for me (note the motif21 directory).

Thanks!