Bugzilla – Bug 272662
GroupWise Messenger client fails due to bug in included java
Last modified: 2007-08-08 10:19:48 UTC
novell-messenger-client-2.0.1-20060522 java: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. See bugs 252510 and 256461. This may also cause the client update to fail - I get an error message that the download failed to complete.
Since Novell does *not* seem to have *any* contacts to SUN Java developers this needs to be workarounded with a wrapper script, which sets LIBXCB_ALLOW_SLOPPY_LOCK environment variable and executes the java binary afterwards.
Bump! GWIM always fails on 100% of machines on 10.3, and the wrapper script is trivial...
BTW, I can't find a single changelog entry in the package by the official maintainer. I suggest to simply fix it and submit the package for 10.3.
I looked into this for groupwise-gwclient but the package is a nosrc, getpac delivers a finished RPM containing the existing /usr/bin/groupwise - and munging that would probably break its checksum. GWIM is also closed source, so someone with access to that build system needs to do it.
I thought that /opt/novell/groupwise/client/jre/bin/java needs to be replaced by a wrapper script as it's also done for other Java versions. But obviously I was wrong (it seems it uses libjava.so instead). Instead /usr/bin/groupwise needs to become a wrapper script, which sets LIBXCB_ALLOW_SLOPPY_LOCK.
/usr/bin/groupwise is already a shellscript, but it's in the inner rpm that only the maintainer can pokle.
fixed.
*** Bug 256461 has been marked as a duplicate of this bug. ***