Bug 969017

(In reply to peter.senna from comment #0)

What has happened is that some dependency of the CDT is not being met and causing it not to load or an exception has occurred within the CDT.

Can you look at the Error Log and add it as an attachment please.  Help -> About Eclipse SDK -> Installation Details -> Configuration -> Show Error Log

If you go to Help -> About Eclipse SDK -> Installation Details -> Plug-ins you will see a list of loaded plugins.  Look for the ones with CDT in them and report that here.  If there is a dependency issue, there will be missing CDT plug-ins.

Created attachment 915719 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Hmm, not being able to see the error log is not good.  Your CDT plug-ins are not loaded from the data above.

Can you start your Eclipse with -clean -consoleLog -debug options and then add the results here?  If you redirect output to a file, then it will be easy to attach the results here.

Just a small amendment to Jeff's Comment #3 : Make sure to create a file called '.options' with the following content :

org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true

in the same location that you run the eclipse command.

Created attachment 755037 [details]
log.out

$ cd /tmp

$ cat .options
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true

$ /usr/lib64/eclipse/eclipse -clean -consoleLog -debug &> log.out

log.out is attached.

I have an F19 VM that's up to date and seems to have no issues with the Eclipse CDT. I have a list of the installed rpms here : http://rgrunber.fedorapeople.org/rpms19.txt Is there perhaps some underyling package that isn't updated and could be causing this ?

Also if you run 'eclipse -nosplash -noexit -console' , and run 'ss cdt', you should see the cdt bundles listed. Do any of them have a state of 'INSTALLED' listed ? Also what do you see when you run 'ss -s INSTALLED' ?

I have installed Fedora from the Beta live DVD.

$ eclipse -nosplash -noexit -console
____________________________
Welcome to Apache Felix Gogo

g! ss cdt
"Framework is launched."


id	State       Bundle
g!

After doing yum update today, it was magically fixed. Thank you very much.

It looks like the reconciler was dropping the cdt bundles for some reason, and so they were not even showing up in the osgi runtime. Eclipse Kepler RC2 is now in updates-testing so perhaps this solved the issue. I'm going to mark this as CLOSED (UPSTREAM) given that the resolution was to update to a newer release candidate.

If this bug appears again on f19 for a newer version of Eclipse CDT, then we can reopen, and investigate further.

The problem returned when updated to eclipse-cdt.x86_64 1:8.2.0-0.7.rc2.fc19, eclipse-cdt-sdk.x86_64 1:8.2.0-0.7.rc2.fc19

This may be an issue with the reconciler itself. Unless it is fully diagnosed, please use this workaround:

sudo touch /usr/lib64/eclipse/configuration/config.ini

it should force your Eclipse to reinstall all plugins.

Krzysztof Daniel, this is not a good solution, at all. Even if fixed the issue I reported.

I'm using Fedora and yum as package source. I do not want that Eclipse download software from Eclipse website. I only trust Fedora rpm packages as I understand how it works.

The Migration Wizard has started, took some minutes to finish and downloaded something from Eclipse website. The problem may still exist even if it is working for me again.

How to revert so my Eclipse will not download updates / modules / anything from Eclipse site?

I don't agree that this is a solution. I can remove Eclipse from my machine and remove all files you ask me to. Then only install packages from yum. Please tell me how.

This do not look as a solution for me.

Peter,

Sorry for those problems. Here is more precise instruction:
1. Touch the config.ini file. This will drop again all downloaded plugins.
2. Cancel the reinstallation wizard (if you don't want to reinstall any upstream bundles) or select only those you really need. At your will.

I know it's not a solution, just a workaround that allows you to work with Eclipse while I'm investigating this issue.

eclipse-4.3.0-0.60.git7bf397.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/eclipse-4.3.0-0.60.git7bf397.fc19

Package eclipse-4.3.0-0.60.git7bf397.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing eclipse-4.3.0-0.60.git7bf397.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-10208/eclipse-4.3.0-0.60.git7bf397.fc19
then log in and leave karma (feedback).

eclipse-4.3.0-0.60.git7bf397.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.