Community
Participate
Working Groups
When starting eclipse from a terminal the following is reported: cjp@workstation6l:~> eclipse libxcb: WARNING! Program tries to unlock a connection without having acquired a lock first, which indicates a programming error. There will be no further warnings about this issue. libxcb: WARNING! Program tries to lock an already locked connection, which indicates a programming error. There will be no further warnings about this issue. This only happens when eclipse is restarted after having created the AddressBook QT project, open the addressbook.ui and exiting eclipse. Platform is openSuSE 10.3, eclipse not installed from distro but eclipse.org download.
(In reply to comment #0) > This only happens when eclipse is restarted after having created the > AddressBook QT project, open the addressbook.ui and exiting eclipse. What is this 'AddressBook QT project'?
It is an QT Integration example from the cheat sheet provided. Let this rest for a while as I need to remove and reinstall eclipse. I'll get back when I'm done.
After having removed all traces of eclipse and installing it afresh to /usr/share, or /usr/local now I get /usr/lib/gecko: No such file or directory on starting eclipse eclipse is eclipse-java-europa-fall2-linux-gtk.tar.gz downloaded from eclipse.org, OS is openSuSE 10.3 There is a bug-buddy report which I attach. Obvoiusly eclipse is expecting /usr/lib/gecko to be a binary, as creating it with touch /usr/lib/gecko results in eclipse "/usr/lib/gecko": not in executable format: File format not recognized There is no package providing /usr/lib/gecko in the openSuSE repositories.
Created attachment 82734 [details] bug-buddy error report on the incident
WFT?
This sounds like an OpenSUSE 10.3 problem; take a look at the following link which describes this problem: http://www.suseforums.net/index.php?showtopic=40943&mode=threaded&pid=207367 The short of it is you need to download Eclipse from either here: http://software.opensuse.org/search or here: http://download.opensuse.org/distribution/...ss/suse/noarch/ Closing as NOT_ECLIPSE
This is making life easy for you. Eclipse is demanding /usr/lib/gecko the link you devise turns up a lot of crap from people not knowing the whereabouts of eclipse and I doubt they are knowledgeable about SusE either. As far as rumours go Java based apps are supposed to be independent of target systems properties, so why don't you just fix it ?
swt integrates with the platform, so there is a lot of potential for it to be affected by the target environment. I don't think that this is an swt bug. However, as a data point, can you see if anything changes if you set environment variable MOZILLA_FIVE_HOME=/dev/null before running eclipse?
No, setting MOZILLA_FIVE_HOME=/dev/null does not seem to influence the behavior. But in the meantime I found, that eclipse behaves as expected when started as root, while when started as normal user it keeps throwing /usr/lib/gecko: No such file or directory. at me whenever anything like welcome or help is called and the mouse pointer moved in. As eclipse also displays this behavior when unpacking the eclipse-SDK-3.3.1.1-linux-gtk.tar.gz as user into a user directory and starting from there, I gather it's nothing to do with Linux rights and permissions. Another indication for this assumption is, that simply no component /usr/lib/gecko exists. Otherwise it could have been lack of rights / permissions as Linux seems to rather tell you "it's not there" than telling you "it's there, but just keep off" Also the unstillable longing for /usr/lib/gecko when run as user indicates to me that there must be some clue in the eclipse package. The gecko component is ( to my knowledge ) not used by any Distribution under this name. They seem to use xulrunner instead, which surely doesn't contain any component located at /usr/lib/gecko.
Grant, this looks like a browser thing. Take ownership?
Created attachment 90675 [details] java .class that prints mozilla path being used Revisiting, attached is a .class file that opens a Browser and prints the location of its native GRE. I'm providing it in this form since you're not able to start eclipse as a non-root user. Can you run it as root and non-root and paste the results here? To run it use a line like: java -cp eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.4.0.v3428.jar:. DisplayMozillaVersion
I am afraid I need some assistance in helping you track this issue. Eclipse is currently installed in /usr/local/eclipse /usr/local/eclipse/plugins does not contain org.eclipse.swt.gtk.linux.x86_3.4.0.v3428.jar but rather org.eclipse.swt.gtk.linux.x86_3.3.1.v3346i.jar org.eclipse.swt.gtk.linux.x86_3.3.2.v3347.jar I downloaded DisplayMozillaVersion.class to /usr/local/eclipse/plugins Running java -cp org.eclipse.swt.gtk.linux.x86_3.3.2.v3347.jar:.DisplayMozillaVersion results only in the help information being displayed. Currently running from openSuSE 11.0 alpha2 with rpm -qa | grep java java-1_5_0-gcj-compat-1.5.0.0-32 java-1_6_0-sun-1.6.0.u4-12 java-1_5_0-sun-plugin-1.5.0_update14-12 javamail-1.4-158 java-1_5_0-sun-1.5.0_update14-12 Running directly from /usr/local/eclipse/plugins omitting the -cp results in java org.eclipse.swt.gtk.linux.x86_3.3.1.v3346i.jar:.DisplayMozillaVersion Exception in thread "main" java.lang.NoClassDefFoundError: org/eclipse/swt/gtk/linux/x86_3/3/1/v3346i/jar:/DisplayMozillaVersion Caused by: java.lang.ClassNotFoundException: org.eclipse.swt.gtk.linux.x86_3.3.1.v3346i.jar:.DisplayMozillaVersion at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) Note that all dots (".") are interpreted as slashes ("/") Please advise
P.S. Also note: I can run eclipse both, as user as well as root. The difference lies in the presence of the bug: If invoked as root the problem is absent and help can be used. If invoked as user as soon as the welcome screen is visible AND cursor moved inside that window a bug buddy report is triggered and eclipse exits. As long as you stay away from browser based content eclipse runs fine as user.
> Running > java -cp org.eclipse.swt.gtk.linux.x86_3.3.2.v3347.jar:.DisplayMozillaVersion > results only in the help information being displayed. I'm not sure if this was a typo in your comment or not, but there should be a space between '.' and "DisplayMozillaVersion". But better, since you can run eclipse (carefully) as a non-root user, you can create the class in eclipse (source below) and run it. Also, in comment 0 you specified OpenSuSE 10.3, and in comment 12 you're on OpenSuSE 11 alpha2. Since the latter is a work-in-progress, for this report please stick to OpenSuSE 10.3. public class DisplayMozillaVersion { public static void main(String[] args) { Device.DEBUG = true; Display display = new Display(); Shell shell = new Shell(display); System.out.println(">>>Snippet creating SWT.MOZILLA-style Browser"); try { new Browser(shell, SWT.MOZILLA); System.out.println(">>>succeeded"); } catch (Error e) { System.out.println(">>>This failed with the following error:"); e.printStackTrace(); System.out.println("\n\nSnippet creating SWT.NONE-style Browser"); try { new Browser(shell, SWT.NONE); System.out.println(">>>succeeded"); } catch (Error e2) { System.out.println(">>>This failed too, with the following error:"); e.printStackTrace(); } } display.dispose(); } }
It actually was mistyped. thanks for pointing that out. Rerunning returns: java -cp /usr/local/eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.3.2.v3347.jar:. DisplayMozillaVersion >>>Snippet creating SWT.MOZILLA-style Browser XULRunner path: /usr/lib/xulrunner-1.8.1.11/libxpcom.so >>>succeeded being invoked as root as well as user
I notice in the bug-buddy error report that the xulrunner library being used is /usr/lib/xulrunner-1.8.1.4/libxul.so, which is different from comment 15. Has your machine changed in the meantime, or do you have both of these? It's also strange that there's a behaviour change between root and non-root users. Do either of them define an environment variable like LD_LIBRARY_PATH or MOZILLA_FIVE_HOME that could be affecting the dependent libraries that get loaded?
"I notice in the bug-buddy error report that the xulrunner library being used is /usr/lib/xulrunner-1.8.1.4/libxul.so, which is different from comment 15. Has your machine changed in the meantime, or do you have both of these?" Your observation is correct, machines get updated over time ( This incident reported 2007-11-11 ). The current state is: workstation6l:/ # rpm -qa | grep xul mozilla-xulrunner181-devel-1.8.1.11-16 mozilla-xulrunner181-l10n-1.8.1.11-16 mozilla-xulrunner181-1.8.1.11-16 "It's also strange that there's a behaviour change between root and non-root users. Do either of them define an environment variable like LD_LIBRARY_PATH or MOZILLA_FIVE_HOME that could be affecting the dependent libraries that get loaded?" This is indeed strange, but both mentioned variables are empty for user as well as root. cjp@workstation6l:~> echo $LD_LIBRARY_PATH cjp@workstation6l:~> echo $MOZILLA_FIVE_HOME cjp@workstation6l:~> su Password: workstation6l:/ # echo $LD_LIBRARY_PATH workstation6l:/ # echo $MOZILLA_FIVE_HOME workstation6l:/ # rpm -qa | grep xul mozilla-xulrunner181-devel-1.8.1.11-16 mozilla-xulrunner181-l10n-1.8.1.11-16 mozilla-xulrunner181-1.8.1.11-16 In addition you may note that defining an "external Browser" via "Window/Preferences/WebBrowser/Use external Webbrowser" does not make any difference. I tried both, Firefox as well as Epiphany.
Just trying this whole issue over booting from a Fedora7 live CD, invoking eclipse from the openSuSE installation. Eclipse is running nicely as user as well as root. java -cp /mnt/suse/usr/local/eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.3.2.v3347.jar:. DisplayMozillaVersion returns: >>>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(SWT.java:3589) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:280) at org.eclipse.swt.browser.Browser.<init>(Browser.java:109) at DisplayMozillaVersion.main(DisplayMozillaVersion.java:17) Snippet creating SWT.NONE-style Browser >>>This failed too, with the following error: org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(SWT.java:3589) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:280) at org.eclipse.swt.browser.Browser.<init>(Browser.java:109) at DisplayMozillaVersion.main(DisplayMozillaVersion.java:17) rpm -qa | grep xul returns nothing [root@localhost plugins]# echo $LD_LIBRARY_PATH [root@localhost plugins]# echo $MOZILLA_FIVE_HOME [root@localhost plugins]# rpm -qa | grep java java-1.5.0-gcj-devel-1.5.0.0-14.fc7 java_cup-0.10-0.k.6jpp.1 gcc-java-4.1.2-27.fc7 java-1.5.0-gcj-1.5.0.0-14.fc7 Need to check this when back in openSuSE. So it appears, that this is an openSuSE issue after all. Still confused where the situation in comment #3 is coming from. Could that be the java implementation ?
This is getting slightly peculiar: After installing openSuSE fresh, the problem persists. But... if logging in as "user", then doing "su user" then invoking eclipse it works!!! Copied from Terminal: cjp@workstation6l:/media/WS6L-Extern1___/Downloads> cd eclipse cjp@workstation6l:/media/WS6L-Extern1___/Downloads/eclipse> ./eclipse /usr/lib/gecko: No such file or directory. cjp@workstation6l:/media/WS6L-Extern1___/Downloads/eclipse> su cjp Password: cjp@workstation6l:/media/WS6L-Extern1___/Downloads/eclipse> ./eclipse ----after quitting eclipse from within----- cjp@workstation6l:/media/WS6L-Extern1___/Downloads/eclipse> Sorry for the trouble and thanks for your assistance!
Might be Evolution after all: As I found out setting the environment variable MALLOC_CHECK_ from "2" to "1" causes Eclipse to run properly, but causes floods of: *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b0801f8 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b182928 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b18a488 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b18a2d0 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b167cc0 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b3a0410 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b3a04f0 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b3a0280 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b391bd0 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b0974e8 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b096310 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b0975a8 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b415e70 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0a828118 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0a8f2330 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b181b70 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0b143250 *** *** glibc detected *** /media/WS6L-Extern1/Downloads/eclipse/eclipse: free(): invalid pointer: 0x0a9b8418 *** Please check whether this could be Eclipse caused or is rather something amiss in glibc
Isn't that interesting, it looks like the Browser's auto-gen'd mappings between java and C++ values of type PRBool are wrong. It has been mapping PRBool to java boolean, but at the C level sizeof(jboolean) is 1 and sizeof(PRBool) is 4. I don't know if this would actually be responsible for your problem or not, but since it needs fixing regardless I'll add a comment here when this is done.
*** Bug 215857 has been marked as a duplicate of this bug. ***
Bug 199842 may be related as well according to https://bugzilla.novell.com/show_bug.cgi?id=293439#c55 , please check.
I've released a large change set that fixes the problem of using the wrong size variable to access PRBools. This has made the "...invalid pointer" messages go away when MALLOC_CHECK_ == 1, and has also fixed several bugs that I did not know existed in the Browser when run on PPC (because it's big-endian). Please try a nightly build for March 5th or later and let me know if it fixes your problem. Or alternatively, you can get swt from cvs as described in http://www.eclipse.org/swt/cvs.php and self-host with it (a.k.a. Run As... Eclipse Application).
"Please try a nightly build for March 5th or later and let me know if it fixes your problem." I'd rather go with this option :-) Only: where do I find nightly builds for eclipse ?
It will appear on http://download.eclipse.org/eclipse/downloads/ beside the "3.4 Stream Nightly Build" label. You'll just have to wait until tomorrow or later for a build that contains the fix.
*** Bug 218200 has been marked as a duplicate of this bug. ***
It seems like there are more reports of this coming up, so I'm changing the summary to reflect the problem trigger. Also note that it looks like the nightly build failed last night, so the released fix won't be testable today.
Looks like you fixed it :-) Running eclipse from untared eclipse-SDK-N20080306-0100-linux-gtk.tar.gz performs nice and smooth. MALLOC_CHECK_=1 doesn not show any output any more apart from malloc: using debugging hooks every now and then. Thanks a lot!
That's great to hear! I don't think this would have been tracked down easily without your observation in comment 20, so thanks for that. I think there may be a couple other reports that will be fixed as a side effect of this as well. Fixed > 0305. For my information, did you set the MALLOC_CHECK_=2 environment variable initially or was it just like that in your linux distro?
For whatever reason it seems to be set =2 for user and =0 for root by default in openSuSE (10.3 and 11.0 alpha).
Grant, somehow I don't seem to be able to get CDT running in the Eclipse SDK, Version: 3.4.0, Build id: N20080310-0100 so it seems I got rid of the bug at the cost of C++ development (IDE) What am I missing ?
I wouldn't think that CDT failing would be connected to this. Nightly builds are often unstable, and the Browser changes should not be visible to clients unless a mistake was made somewhere. How does CDT fail for you? Is there anything useful in the Error Log view? Do the CDT plug-ins appear in Help > About Eclipse SDK > Plug-in Details?
Thanks for getting back on this. Actually CDT doesn't fail. It just refuses to be installed :-( I used to use http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/europa/winter/eclipse-cpp-europa-winter-linux-gtk.tar.gz but that's still containing the bug. and from http://download.eclipse.org/eclipse/downloads/eclipse-SDK-N20080306-0100-linux-gtk.tar.gz I don't seem to be able to install CDT :-(
Can you install CDT with the eclipse build from http://download.eclipse.org/eclipse/downloads/drops/I20080305-1100/index.php ? This is the latest eclipse integration build that does not contain the fix.
http://build.eclipse.org/technology/epp/epp_build/34/download/20080311-0800/20080311-0800_eclipse-cpp-ganymede-M5-linux.gtk.x86.tar.gz is the latest cpp I could find, and it still contains the bug http://download.eclipse.org/eclipse/downloads/drops/I20080305-1100/download.php?dropFile=eclipse-SDK-I20080305-1100-linux-gtk.tar.gz is marked with an red X not a green check
> [the eclipse build] is marked with an red X not a green check It should be fine to download and try, the red 'X' means it failed one or more unit tests, but this is not likely to affect CDT startup.
As with the other package I get: Unsatisfied dependency: [org.eclipse.cdt.sdk.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.source.feature.group/[3.0.1,3.0.1] Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.views/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.editors/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.boot/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.compare/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.runtime.compatibility/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.debug.ui/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.filebuffers/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.resources/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jface.text/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.console/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.team.core/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.sdk.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.source.feature.group/[3.0.1,3.0.1] Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.search/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.ide/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.debug.core/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench.texteditor/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.sdk.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.source.feature.group/[3.0.1,3.0.1] Unsatisfied dependency: [org.eclipse.cdt.sdk.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.cdt.feature.group/[3.0.1,3.0.1] Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.team.core/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.editors/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.compare/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jface.text/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.boot/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.debug.core/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.filebuffers/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.search/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.workbench.texteditor/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.debug.ui/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.resources/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.views/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.ide/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.ui.console/0.0.0 Unsatisfied dependency: [org.eclipse.cdt.feature.group 3.0.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.core.runtime.compatibility/0.0.0
So it looks like cdt was failing in the 3.4 stream before this fix was made. See if anyone on the CDT newsgroup or bugzilla has brought this up, and if not then I would suggest posting a question to the cdt newsgroup. With that many failures either they must be aware of it or perhaps your install has gone bad somehow (?). As a workaround in the meantime, if the CDT 0311 build works but has the browser bug, you could probably take the swt jars from your eclipse nightly build and drop them into the CDT installation (remember to remove the old swt jars from it).
Thanks for your helpful comments. I got it up and running now without the bug and with CDT.
It would have been _a_lot_easier_ from comment #32, had I stumbled on "What's New" earlier :-( See Bug 222378
*** Bug 199842 has been marked as a duplicate of this bug. ***
*** Bug 233951 has been marked as a duplicate of this bug. ***
*** Bug 207222 has been marked as a duplicate of this bug. ***
