Red Hat Bugzilla – Bug 238066
Clean install of Eclipse 3.2.2 fails to start
Last modified: 2007-11-30 17:12:03 EST
Description of problem: Version-Release number of selected component (if applicable): eclipse-sdk.i386 1:3.2.2-1.fc6 How reproducible: I've done this now 3 times. Steps to Reproduce: 1. On FC6 freshly upgraded from FC5, remove all eclipse packages and dependencies. 2. Delete all remaining eclipse and workspace directories in user directories and delete /usr/share/eclipse. 3. do a fresh install of eclipse using yum install eclipse-pde-devel eclipse-cdt Actual results: Eclipse platform displays an error popup on startup: An error has occurred. See the log file /root/workspace/.metadata/.log. Expected results: Platform starts and displays welcome window. Additional info:
Created attachment 153555 [details] Error log from ~/workspace/.metadata
Ok, it's a little strange that you're running eclipse as root. You shouldn't do that if you can help it because eclipse will write configuration files to /usr/share/eclipse/ which will mess up eclipse for other users on the system. Here's what you should do: * remove eclipse again: sudo yum remove eclipse-rcp libswt3-gtk2 eclipse-ecj * manually delete /usr/share/eclipse and /usr/lib/eclipse sudo rm -r /usr/share/eclipse /usr/lib/eclipse * install eclipse sudo yum install eclipse-sdk eclipse-cdt * run eclipse as a normal user. If you still have a problem then you should move ~/.eclipse to out of the way and try again: mv ~/.eclipse{,.bak} If this works I'd like to see your backed up ~/.eclipse. Please report back. Thanks, Ben
Yeah, I know I shouldn't run it as root, but its the only way to install subclipse. If you run it as a normal user, the subclipse installation fails with an error message that it doesn't have write permission on some directory (don't remember which). I notice that there is an update for eclipse available today. I'll follow up after I've run through your instructions. Thanks, Ted
I've followed the steps above, and eclipse now starts up correctly. There are, however, some additional problems. I will put in a new bug report on those now.
Ok, so can we close this bug?
Go ahead and close it. It sounds as if you have identified the problem. I'll test the latest release when it hits the update sites.
*** This bug has been marked as a duplicate of 238107 ***