This technote explains how to resolve a java runtime exception error, "Widget disposed too early", that might occur when using IBM® Rational® ClearQuest® in a Linux® environment.
After installing ClearQuest, the ClearQuest Eclipse Client (RCP) will not start. In the ClearQuest installation.log file you might find the following error:
!ENTRY org.eclipse.ui.workbench 4 0 2007-03-27 14:39:07.61
!MESSAGE Widget disposed too early!
java.lang.RuntimeException: Widget disposed too early!
Similarly, ClearQuest may start but then the splash screen errors out referring to a log file that has the widget error above and the following SWTError:
!ENTRY org.eclipse.osgi 2008-04-25 14:29:19.298
!MESSAGE Application error
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
The root cause is that the Standard Widget Toolkit (SWT) runtime can not find or initialize the installed browser.
Note: This can also occur if there are problems with the version of xulrunner installed. For example, if you have mozilla-xulrunner on SUSE Linux, running an rpm -e command against the package might resolve the problem. For more information on this, see techote 1394977.
Resolving the problem
The SWT FAQ offers a solution to resolve this issue. Notice the section specifically about a bug with IBM 1.4 VMs that may keep the necessary libraries of the LD_LIBRARY_PATH environment variable. The following section is copied from the SWT FAQ:
|Q: How can I get the SWT Browser to work with the IBM 1.4 VM?
A: The IBM 1.4 VM accidentally removes certain entries of the environment variable LD_LIBRARY_PATH. This occurs in particular for entries starting with /usr/lib. It will leave untouched entries such as /usr/../usr/lib.
Instructions for Red Hat Enterprise Linux 3 users:
Note: These instructions are for RHEL 4 and 5 as well.