Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 233841 - SWT XPCOM error w/ xulrunner-1.9.0 from openSUSE
Summary: SWT XPCOM error w/ xulrunner-1.9.0 from openSUSE
Status: RESOLVED DUPLICATE of bug 213194
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-25 06:38 EDT by Michael Woski CLA
Modified: 2008-05-27 13:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Woski CLA 2008-05-25 06:38:50 EDT
Build ID: 3.4RC2

I'm running openSUSE 11 (beta something) and have installed xulrunner 1.9.0-8 from their build server. Trying to run eclipse isn't possible because I'm getting an XPCOM error caused from loading the IntroPage. 

Following should be the interesting part of the log file output:

org.eclipse.swt.SWTError: XPCOM error -2147467262
	at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1597)
	at org.eclipse.swt.browser.Mozilla.setText(Mozilla.java:1820)
	at org.eclipse.swt.browser.Browser.setText(Browser.java:733)
	at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartImplementation.generateContentForPage(BrowserIntroPartImplementation.java:252)
	at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartImplementation.dynamicStandbyStateChanged(BrowserIntroPartImplementation.java:451)
	at org.eclipse.ui.internal.intro.impl.presentations.BrowserIntroPartImplementation.doStandbyStateChanged(BrowserIntroPartImplementation.java:658)
	at org.eclipse.ui.internal.intro.impl.model.AbstractIntroPartImplementation.standbyStateChanged(AbstractIntroPartImplementation.java:249)
	at org.eclipse.ui.internal.intro.impl.model.IntroPartPresentation.standbyStateChanged(IntroPartPresentation.java:443)
	at org.eclipse.ui.intro.config.CustomizableIntroPart.standbyStateChanged(CustomizableIntroPart.java:266)
	at org.eclipse.ui.internal.ViewIntroAdapterPart$2.run(ViewIntroAdapterPart.java:74)
Comment 1 Grant Gayed CLA 2008-05-26 09:36:08 EDT
I believe the xulrunner version is 1.9.0-a8, which is a 1.9-stream alpha release whose nsIDocShell has changed its IID in the meantime.  XULRunner 1.9 has not been released yet, though it's now close, so the set of interface IIDs in its recent builds are the ones considered to be "correct" for 1.9.  I'm quite sure that this will work for you with a recent xulrunner 1.9-stream build such as http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/ .

Closing as WONTFIX on the assumption that this is the problem.  If you still see this with a recent xulrunner build then please reopen this report.
Comment 2 Michael Woski CLA 2008-05-26 11:02:42 EDT
thanks for the quick response, but I doubt that this is really the issue here. In fact version 1.9.0-8 is definitely one of the latest builds which I also use with Firefox 3.0rc1.
Does an elfread of whichever file help?
Comment 3 Grant Gayed CLA 2008-05-26 12:50:24 EDT
can you paste the result of running: ./xulrunner --v
Comment 4 Michael Woski CLA 2008-05-27 01:56:46 EDT
the version is Mozilla XULRunner 1.9.0 - 2008051400
Comment 5 Gilberto Olimpio CLA 2008-05-27 12:37:52 EDT
I'm having the same problem on Ubuntu 8.04 running Firefox 3 RC1

This error only occurs on Eclipse 3.4 RC2, I'm running 3.4 M7 with no problems.

Mozilla XULRunner 1.9 - 2008052515
Comment 6 Grant Gayed CLA 2008-05-27 13:20:33 EDT
It has been pointed out that the nsIDocShell interface has changed in mozilla during their Release Candidate builds (?!?), see https://bugs.eclipse.org/bugs/show_bug.cgi?id=213194#c14.  Marking this report as a duplicate, this will be fixed for 3.4RC3.


*** This bug has been marked as a duplicate of bug 213194 ***