Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8566 - Java app not working even with libx11 update

Attached to Project: Arch Linux
Opened by Jordi Cerdan (jcerdan) - Thursday, 08 November 2007, 07:59 GMT
Last edited by Alexander Baldeck (kth5) - Friday, 09 November 2007, 01:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Alexander Baldeck (kth5)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am trying to install Zend Studio and I receive the following error:
java: xcb_xlib.c:82: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

This seems exactly the bug #8251 (I can't re-open it).

My system is up to date and freshly installed it 2 days ago.

Everytime I try to install Zend Studio it crashes and I can't install it.

This is the output:
--------------------------------------------------------------------------
Preparing to install...

Extracting the JRE from the installer archive...

Unpacking the JRE...

Extracting the installation resources from the installer archive...

Configuring the installer for this system's environment...



Launching installer...



Locking assertion failure. Backtrace:

#0 /usr/lib/libxcb-xlib.so.0 [0xb7f56767]

#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7f568b1]

#2 /usr/lib/libX11.so.6(_XReply+0xfd) [0xb1d59a8d]

#3 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/xawt/libmawt.so [0xb2857a76]

#4 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/xawt/libmawt.so [0xb283d80a]

#5 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/xawt/libmawt.so [0xb283da51]

#6 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/xawt/libmawt.so(Java_sun_awt_X11GraphicsEnvironment_initDisplay+0x24) [0xb283dc5c]

#7 [0xb2af18ee]

#8 [0xb2aeba7b]

#9 [0xb2aeba7b]

#10 [0xb2ae9157]

#11 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/client/libjvm.so [0xb77e3fec]

#12 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/client/libjvm.so [0xb78f11f8]

#13 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/client/libjvm.so [0xb77e3e1f]

#14 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/client/libjvm.so(JVM_DoPrivileged+0x32d) [0xb78414bd]

#15 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/libjava.so(Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0x3d) [0xb76032cd]

#16 [0xb2af122e]

#17 [0xb2aeb9a4]

#18 [0xb2ae9157]

#19 /tmp/install.dir.8481/Linux/resource/jre/lib/i386/client/libjvm.so [0xb77e3fec]

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

--------------------------------------------------------------------
This task depends upon

Closed by  Alexander Baldeck (kth5)
Friday, 09 November 2007, 01:26 GMT
Reason for closing:  Fixed
Comment by Ondrej Jirman (megous) - Thursday, 08 November 2007, 11:25 GMT
Same here with azureus. Similar backtrace. (it does not fail immediatelly, but after adding new file for download)

(SWT:8024): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 250 and height -1
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb7fb1767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7fb18b1]
#2 /usr/lib/libX11.so.6(_XReply+0xfd) [0x8fa50a9d]
#3 /opt/java/jre/lib/i386/xawt/libmawt.so [0x8bf8a64e]
#4 /opt/java/jre/lib/i386/xawt/libmawt.so [0x8bf68f97]
#5 /opt/java/jre/lib/i386/xawt/libmawt.so [0x8bf69248]
#6 /opt/java/jre/lib/i386/xawt/libmawt.so(Java_sun_awt_X11GraphicsEnvironment_initDisplay+0x2f) [0x8bf6954f]
#7 [0xb4d86b7b]
#8 [0xb4d7ef0d]
#9 [0xb4d7ef0d]
#10 [0xb4d7c243]
#11 /opt/java/jre/lib/i386/server/libjvm.so [0x62c5ecd]
#12 /opt/java/jre/lib/i386/server/libjvm.so [0x64523b8]
#13 /opt/java/jre/lib/i386/server/libjvm.so [0x62c5d60]
#14 /opt/java/jre/lib/i386/server/libjvm.so(JVM_DoPrivileged+0x34b) [0x631bc1b]
#15 /opt/java/jre/lib/i386/libjava.so(Java_java_security_AccessController_doPrivileged__Ljava_security_PrivilegedAction_2+0x3d) [0xb7d8696d]
#16 [0xb4d86b7b]
#17 [0xb4d7eda7]
#18 [0xb4d7c243]
#19 /opt/java/jre/lib/i386/server/libjvm.so [0x62c5ecd]
java: xcb_xlib.c:82: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
/usr/bin/azureus: line 3: 8024 Aborted java -cp "${CLASSPATH}" -Dazureus.install.path=${HOME}/.azureus/ org.gudy.azureus2.ui.swt.Main "$@"
Comment by Ondrej Jirman (megous) - Thursday, 08 November 2007, 11:29 GMT
It seems like a common problem with java, these days...

https://bugs.launchpad.net/ubuntu/+source/sun-java5/+bug/86103
Comment by Ondrej Jirman (megous) - Thursday, 08 November 2007, 11:31 GMT
And it can be worked around by using export LIBXCB_ALLOW_SLOPPY_LOCK=true. Azureus then works for me (dumps some backtraces, but works).
Comment by Jan de Groot (JGC) - Thursday, 08 November 2007, 12:07 GMT
Update to libx11 1.1.3-6 and login again to make the changes permanent.
Comment by Jordi Cerdan (jcerdan) - Thursday, 08 November 2007, 12:26 GMT
Yes, I upgdated libx11 yesterday and I encounter the same problem.

I have found something interesting: In fact, I run Zend Studio install using sudo, this is important for me so that Zend is installed in /usr/local/Zend directory. If I run the install program with user permission only, it's only allowed to install it on the user's home.

I have tried to run the installer without sudo, and it started fine. Using sudo gives me always the same error.

As explained before, it's important for me to install it using sudo (I have made this before in other computers running Arch without any problems).
Comment by Jordi Cerdan (jcerdan) - Thursday, 08 November 2007, 12:29 GMT
Ok, I installed it as root and now it goes fine...I don't know why before I could install it using sudo and not now...
Comment by Jan de Groot (JGC) - Thursday, 08 November 2007, 12:36 GMT
This is because sudo cleans your environment so you won't pass dirty environment variables to a program running as root.

Loading...