Red Hat Bugzilla – Bug 185539
Eclipse crashes with log file indicating that the problem lies in (java class?) org.eclipse.core.resources
Last modified: 2007-11-30 17:11:27 EST
Description of problem:
Eclipse crashes emidietly after splash screen has been completed.
A crash window indicates the following:
An error has occurred. See the log file
The log file indicates the following (seems like the key problem):
!ENTRY org.eclipse.osgi 2006-03-14 17:48:51.24
!MESSAGE An error occurred while automatically activating bundle
Entire log is included.
Version-Release number of selected component (if applicable):
Happens every time I start it up.
Steps to Reproduce:
Unknown. It is likely a problem with a package Eclipse is dependent on. I have
attempted to reinstall all the packages that have to do with Eclipse, but have
been unable to fix the problem.
I have included several log files - one for each of the time that eclipse
crashes. I suspect that only one is needed. diff indicates quite a lot of lines
are different, but that is likely just to be time stamps differing on each line.
To be sure, it's all included.
Created attachment 126155 [details]
log file number 1
Created attachment 126157 [details]
log file number 2
Created attachment 126158 [details]
log file number 3
Created attachment 126159 [details]
log file number 4
Created attachment 126160 [details]
log file number 5
It looks like your workspace is un-writable:
java.lang.IllegalStateException: The platform metadata area could not be
written: /home/clearer/workspace/.metadata. By default the platform writes its
under the current working directory when the platform is launched. Use the
-data parameter to
specify a different content area for the platform.
Removing my workspace and recreating it manually removed the problem. Shouldn't
this be handled in a different way? Say by alerting the user directly that the
workspace is unwritable, or by prompting the user to create a new workspace (or
(In reply to comment #7)
> Removing my workspace and recreating it manually removed the problem. Shouldn't
> this be handled in a different way? Say by alerting the user directly that the
> workspace is unwritable, or by prompting the user to create a new workspace (or
> something similar)?
Yeah, I agree that the error messages could be nicer. Perhaps file upstream as
an enhancement request at bugs.eclipse.org?