Ubuntu
eclipse package

Eclipse doesn't start on current Hardy Heron Alpha 3 anymore - internal browser problem?

Bug #183137 reported by momo
6
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have been working for weeks without problems with the current Eclipse 3.4 M4, Sun JDK 7 preview (oct/dec versions) on my 7.10 Gutsy upgraded to Hardy Heron Alpha (64 bit). Since I do daily upgrades I don't know exactly what actually has been changed to the system since I succesfully started Eclipse last time - but at least I didn't touch neither JDK nor Eclipse.

Since yesterday I get the following stacktrace printed to the console when trying to start Eclipse:

Exception in thread "Thread-1" org.eclipse.swt.SWTError: XPCOM error -2147467262
 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1360)
 at org.eclipse.swt.browser.Mozilla.setText(Mozilla.java:1564)
 at org.eclipse.swt.browser.Browser.setText(Browser.java:716)
 at org.eclipse.jdt.internal.ui.infoviews.JavadocView.setInput(JavadocView.java:531)
 at org.eclipse.jdt.internal.ui.infoviews.JavadocView.refresh(JavadocView.java:452)
 at org.eclipse.jdt.internal.ui.infoviews.JavadocView.setBackground(JavadocView.java:439)
 at org.eclipse.jdt.internal.ui.infoviews.AbstractInfoView.inititalizeColors(AbstractInfoView.java:327)
 at org.eclipse.jdt.internal.ui.infoviews.AbstractInfoView.createPartControl(AbstractInfoView.java:191)
 at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:372)
 at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
 at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
 at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:300)
 at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:531)
 at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
 at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
 at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
 at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:472)
 at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
 at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:668)
 at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:576)
 at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:564)
 at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:270)
 at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:931)
 at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2497)
 at org.eclipse.ui.internal.WorkbenchWindow$23.run(WorkbenchWindow.java:2837)
 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
 at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:2818)
 at org.eclipse.ui.internal.WorkbenchWindow$17.runWithException(WorkbenchWindow.java:2135)
 at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:130)
 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3312)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2985)
 at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:801)
 at org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1344)
 at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:130)
 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3312)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2985)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2315)
 at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2225)
 at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:468)
 at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:463)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
 at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:362)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:623)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:515)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:455)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1193)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1169)

No error log is written.

I googled "XPCOM error -2147467262" and found a number of "solutions" (installing different versions of Firefox, messing around with xulrunner, setting MOZILLA_FIVE_HOME and such, deploying SWT binaries to JDK), but none of them did actually help or "change" the error. I tried Eclipse version 3.3, same problem. I installed Eclipse via apt-get, didn't work - but failed with another error.

If this is a known problem or not a bug at all, any help would be appreciated.

regards,
momo

Related branches

lp:ubuntu/karmic/eclipse
Revision history for this message
Volodymyr Buell (vbuell) wrote :

Absolute the same. Neither stable nor dev builds of eclipse don't work. Firefox version is 2.

Revision history for this message
Koen (koen-beek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in eclipse.

Revision history for this message
momo (momo-gmx) wrote :

Thanks for taking a look. Concerning package association - I really didn't have a clue where to put this report, because the failing program has been working for weeks. So my idea was that the problem must be something else. Thanks for the link clearifying how to choose the right package.

Revision history for this message
Grant Gayed (grant-gayed) wrote :

If the OS has a registered 1.9-stream xulrunner install then you're seeing https://bugs.eclipse.org/bugs/show_bug.cgi?id=213194 . SWT's Browser currently does not work with xulrunner 1.9 (this will be fixed once xulrunner 1.9/firefox 3.0 has reached its code freeze, which should be very soon). In the meantime you can try pointing the Browser at a different native GRE by starting eclipse with -vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=<value> .

Revision history for this message
momo (momo-gmx) wrote :

My Apologies! Sorry, for replying so late. You are certainly right about the SWT/xulrunner bug. As stated in my original post I already tried a number of browser related settings without success. But the -Dorg.eclipse.swt.browser.XULRunnerPath option (pointed to a Firefox 2.0 installation) finally did the trick. Now at least Eclipse starts. It still crashes after a few seconds when starting to compile the workspace, but that's another problem I suggest.

Thank you for your help!

Revision history for this message
Grant Gayed (grant-gayed) wrote :

To update, eclipse 3.4M5 should now work with 1.9-stream xulrunners, so "-vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=<value>" is no longer required. This milestone build was just declared and is available at http://download.eclipse.org/eclipse/downloads/drops/S-3.4M5-200802071530/index.php .

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eclipse - 3.2.2-5ubuntu1

---------------
eclipse (3.2.2-5ubuntu1) hardy; urgency=low

  [ Flávio Martins ]
  * Merge from Debian unstable. Remaining Ubuntu changes:
    - Change maintainer to MOTU in debian/control.in and debian/control
    - Regenerated debian/control for Ubuntu.
  * Build-depend on libxul-dev instead of firefox-dev. Closes LP: #191586
  * Closes LP: #183137 LP: #67858

  [ Emilio Pozuelo Monfort ]
  * debian/control{.in}:
    - Move eclipse-source from eclipse's Depends to Suggests. LP: #67862
  * Commented out icedtea in debian/extra/java_home, since it doesn't work
    and makes eclipse not start if the user has icedtea installed.

 -- Emilio Pozuelo Monfort <email address hidden> Mon, 03 Mar 2008 16:40:56 +0100

Changed in eclipse:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.