XPCOM error -2147467262 with 64bit client ext on Linux mint
Hi all I have installed the following:
RTC Client 3.0.1.2 RTC Client Extension (So can integrated with RSA 8.0.4 64 bit) RSA 8.0.4 When I start up RSA with RTC integrated and when I open Team Advisor view I get the following error: XPCOM Error -2147467262 Here is the full stack trace !SESSION 2012-02-27 02:10:11.739 ----------------------------------------------- eclipse.buildId=unknown java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20110726_87724 (JIT enabled, AOT enabled) J9VM - 20110726_087724 JIT - r9_20101028_17488ifx17 GC - 20101027_AA_CMPRSS BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA Framework arguments: -product com.ibm.rational.rsa.product.v80.ide Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.ibm.rational.rsa.product.v80.ide !ENTRY com.ibm.team.process.ide.ui 4 0 2012-02-27 02:10:35.217 !MESSAGE Error logged from Process Client UI: !STACK 0 org.eclipse.swt.SWTError: XPCOM error -2147467259 at org.eclipse.swt.browser.Mozilla.error(Unknown Source) at org.eclipse.swt.browser.Mozilla.initXULRunner(Unknown Source) at org.eclipse.swt.browser.Mozilla.create(Unknown Source) at org.eclipse.swt.browser.Browser.<init>(Unknown Source) at com.ibm.team.process.internal.ide.ui.advice.TeamAdvisorView.createDetailBrowser(Unknown Source) at com.ibm.team.process.internal.ide.ui.advice.TeamAdvisorView.createPartControl(Unknown Source) at org.eclipse.ui.internal.ViewReference.createPartHelper(Unknown Source) at org.eclipse.ui.internal.ViewReference.createPart(Unknown Source) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(Unknown Source) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(Unknown Source) at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(Unknown Source) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Unknown Source) at org.eclipse.ui.internal.Workbench$31.runWithException(Unknown Source) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(Unknown Source) at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) at org.eclipse.ui.internal.Workbench.runUI(Unknown Source) at org.eclipse.ui.internal.Workbench.access$4(Unknown Source) at org.eclipse.ui.internal.Workbench$7.run(Unknown Source) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source) at org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source) at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source) at org.eclipse.equinox.launcher.Main.run(Unknown Source) at org.eclipse.equinox.launcher.Main.main(Unknown Source) Before I was getting some other errors that asked me to set the MOZILLA_FIVE_HOME and add that to the LD_LIBRARY_PATH. I did all that and also setting the xulrunner path in the eclipse.ini But when I start Rational Team Concert standalone client everything works fine. Any help is appreciated. |
Accepted answer
http://wiki.eclipse.org/IRC_FAQ#Eclipse_gets_past_the_splash_screen_but_then_an_empty_window_appears_.2F_Eclipse_is_crashing_on_me_whenever_I_initiate_a_browser_component_such_as_hovering_over_Java_methods_for_javadoc_tooltips... Thanks for your help. The issue is resolved by adding this line to eclipse.ini to force webkit rendering: -Dorg.eclipse.swt.browser.UseWebKitGTK=true Jared Burns selected this answer as the correct answer
Comments
Jan Van den Audenaerde
commented Oct 08 '12, 5:04 a.m.
The proposed solution (= adding the above line to eclipse.ini) also worked for me.
Thanks for posting this solution. Jan.
|
3 other answers
http://wiki.eclipse.org/IRC_FAQ#Eclipse_gets_past_the_splash_screen_but_then_an_empty_window_appears_.2F_Eclipse_is_crashing_on_me_whenever_I_initiate_a_browser_component_such_as_hovering_over_Java_methods_for_javadoc_tooltips...
That error looks like a known issue with Eclipse. There are some fixes you can try from the Eclipse FAQ. |
I resolved a problem like this by installing the 32-bit version of xulrunner
|
How did you resolve this problem with the 32-bit xulrunner? When I installed that and update the eclipse.ini it started throwing this error: XPCOM error -2147467261
Here is my update to the eclipse.ini file plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520 -vmargs -Xms100m -Xmx512m -Dosgi.requiredJavaVersion=1.5 -Dosgi.bundlefile.limit=100 -Dorg.eclipse.swt.browser.XULRunnerPath=/home/coxda/xulrunner |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.