Bugzilla – Full Text Bug Listing
| Summary: | eclipse 3.6 and 4.0 crash when showing popup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Gaber <Michael.Gaber> | ||||
| Component: | SWT | Assignee: | Grant Gayed <grant_gayed> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | eclipse.felipe, grant_gayed, remy.suen, sven.koehler | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Gaber
Created attachment 177692 [details]
error report file from vm
What versions of GTK+, XULRunner, and Firefox do you have installed on your system? xulrunner: 2.0_beta5_pre-r1 firefox: 4.0_beta5_pre-r1 gtk+: 1.2.10-r12 on a gentoo testing (~x86) box (In reply to comment #3) > xulrunner: 2.0_beta5_pre-r1 > firefox: 4.0_beta5_pre-r1 I'm guessing this is probably the problem. > gtk+: 1.2.10-r12 x11-libs/gtk+ is slotted. You should have a 2.x installation. # equery list x11-libs/gtk+ sure, gtk+ is also in version 2.20.1-r1 installed sry missed that one in the compact output of eix. but well, i think since 4.0 is the next release of firefox and will be released fairly soon, something should be done about this bug. (In reply to comment #5) > but well, i think since 4.0 is the next release of firefox and will be released > fairly soon, something should be done about this bug. Firefox 4.0 is not out yet so it is possible the problem will have resolved itself when it goes GA. On the other hand, it's not even clear if the 4.0 beta is to blame as we have no evidence at the moment to indicate that Firefox 3.6 works for you. I'm actually trying to install an older firefox to test it. i might note that i can without problems run a eclipse 3.5.1-r1 which is built (emerged) on this system with the ff 4 installed (In reply to comment #7) > i might note that i can without problems run a eclipse 3.5.1-r1 which is built > (emerged) on this system with the ff 4 installed It may be worth getting the 3.5.x series from eclipse.org and see if that runs properly then. http://download.eclipse.org/eclipse/downloads/ 3.5.2 crahes exactly the same way, I'll try with 3.5.1 next and afterwards finish the ff change ssdd with 3.5.1 all versions work with firefox-3.6.8-r1 including the emerged one We do not support: xulrunner: 2.0_beta5_pre-r1 firefox: 4.0_beta5_pre-r1 Grant, do you plan to move to a new xulrunner ? Support is never claimed for beta releases of mozilla renderers, and it's not currently planned to implement support for xulrunner 2.0/firefox 4.0 because linux distros that are new enough to include these should also provide WebKitGTK+ as an alternative. The thing I'm wondering about is how did it end up trying to use /usr/lib/xulrunner-2.0/... in the first place, because the xulrunner detection code is given a ceiling of "1.9.*" for acceptable versions. You're not doing anything to explicitly point at /usr/lib/xulrunner-2.0/, right? And does you linux distro really not ship with either a xulrunner version < 2.0 or a WebKitGTK version >= 1.2.0? i dont actually know. I'm using gentoo and have installed the java-overlay via layman. so I basically just emerged firefox-4-beta-whatever and noticed that the binary build of eclipse started to crash on me that day. xulrunner in gentoo is actually slotted only 1.9 and the 2.0 beta versions are also in the 1.9 slot, so i cant have 2 diffeent versions of them installed at the same time i have webkit-gtk installed in version 1.2.3. if i can do anything to help further i will gladly do so Ok, at least there's a usable WebKitGTK+ there. A workaround that should get eclipse running for you is to add the following line to the bottom of your eclipse.ini file: -Dorg.eclipse.swt.browser.UseWebKitGTK=true Setting this property is only needed with eclipse/swt 3.6.x; as of 3.7 WebKitGTK+ is used by default any time it's found on the user's machine, so it should work for you out of the box. Back to xulrunner... > xulrunner in gentoo is actually slotted only 1.9 and the 2.0 beta versions > are also in the 1.9 slot, so i cant have 2 different versions of them > installed at the same time Can you try the following: - add the -D switch above to your eclipse.ini - run eclipse, it should come up fine - run the snippet in https://bugs.eclipse.org/bugs/show_bug.cgi?id=319123#c23 -> what does it print? it prints this. swt-3.6 built on this machine was used, hope that is ok. MOZILLA_FIVE_HOME: /usr/lib/xulrunner-devel-2.0 LD_LIBRARY_PATH: /opt/icedtea6-bin-1.8.1/jre/lib/i386/server:/opt/icedtea6-bin-1.8.1/jre/lib/i386:/opt/icedtea6-bin-1.8.1/jre/../lib/i386:/usr/lib/xulrunner-devel-2.0 >>>Snippet creating SWT.MOZILLA-style Browser >>>This failed with the following error: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.browser.Mozilla.create(Unknown Source) at org.eclipse.swt.browser.Browser.<init>(Unknown Source) at Test.main(Test.java:41) Snippet creating SWT.NONE-style Browser Mozilla path: /usr/lib/xulrunner-devel-2.0 >>>This failed too, with the following error: org.eclipse.swt.SWTError: XPCOM error -1041039104 at org.eclipse.swt.browser.Mozilla.error(Unknown Source) at org.eclipse.swt.browser.Mozilla.initFactories(Unknown Source) at org.eclipse.swt.browser.Mozilla.create(Unknown Source) at org.eclipse.swt.browser.Browser.<init>(Unknown Source) at Test.main(Test.java:48) Marking as a duplicate of bug 319123. Although the symptoms in these reports are different, the cause is the same. This should be fixed for 3.6.2 and later. *** This bug has been marked as a duplicate of bug 319123 *** |