eclipse C++ editor fails to open

[N7DR]

Binary package hint: eclipse

Trying to edit any C++ files I get the message:
  Could not open the editor: No editor descriptor for id org.eclipse.cdt.ui.editor.CEditor

I have a LOT of C++ files and I need either a fix or a workaround for this ASAP in order to do my work.

This is using the lucid eclipse and eclipse-cdt packages from Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: eclipse 3.5.2-6ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Jan 31 16:52:38 2011
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eclipse
xulrunner-versions:
 /usr/lib/xulrunner-1.9.0.4
 /usr/lib/xulrunner-1.9.2.13

[Niels Thykier (niels-thykier)]

Hey,

Could you check if you are suffering from LP: #633198[1]?

~Niels

[1] https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/633198

[N7DR (doc-evans)]

I'm not sure how to check that for certain... https://bugs.launchpad.net/bugs/633198 seems (more or less) just to point to http://bugs.debian.org/587657, which is a very long thread

It probably is the cause of the problem, though, since this is an update, not a fresh install.

However, executing the sed command:
  sed -i 's/^\([^,]*\),[^,]*,\([^,]*\/\1\)_\([^,\/]*\).jar,/\1,\3,\2_\3.jar,/' "$(find ~/.eclipse -name bundles.info)"
doesn't seem to have changed the behaviour :-( Still getting the same problem.

[N7DR (doc-evans)]

Since the sed command didn't work, am I right in thinking that the following is more likely to "fix" the problem:

1. Uninstall the eclipse and eclipse-cdt packages
2. Remove my ~/.eclipse durectory
3. Installthe eclipse and eclipse-cdt packages

If that is supposed to work, how much of importance am I going to have to re-do to get the configuration back to the way I have currently have it, having deleted my current ~/.eclipse directory?

[N7DR (doc-evans)]

Replying to self, I did those three steps, and now I can at least see my C++ files. It remains to be seen if I've messed anything up, but at least I appear to be able to work again.