Red Hat Bugzilla – Bug 210764
[packaging bug] configuration/org.eclipse.update/platform.xml has references to fetures to all SDK features
Last modified: 2007-11-30 17:11:45 EST
Description of problem:
I did a fresh install of eclipse and tried to do help->software updates->find
and install and I got the error dialog shown in the screen shot attachement. It
lets me proceed and I try and add some additional modules from the calisto site,
but then I get the same error when I select any module and it doesn't let me
Version-Release number of selected component (if applicable):
always after a fresh install of eclipse
Steps to Reproduce:
2.try and add a new module using help->software udpates->find and install
error message about file not found
no error message.
I started eclipse as root and the selected help->software updates->find and
install. I then exited eclipse and restart as a normal user. This cleared the
problem and now I can add modules as a normal user
Created attachment 138507 [details]
Screenshot of error message
(In reply to comment #1)
> Created an attachment (id=138507) 
> Screenshot of error message
Hmm, this isn't a screenshot of the error message. Could you please attach your
(In reply to comment #0)
> I started eclipse as root and the selected help->software updates->find and
> install. I then exited eclipse and restart as a normal user. This cleared the
> problem and now I can add modules as a normal user
You shouldn't run eclipse as root because it writes configuration data in
/usr/share/eclipse/configuration. This locks eclipse into set configuration
because non-root users can't write to /usr/share/eclipse/configuration. It is
for this reason running eclipse as root is unsupported.
Created attachment 138520 [details]
Screenshot of error message
I've corrected the screenshot (sorry too quick with the file selection)
Also, yes I know that one isn't supposed to run eclipse as root, but by doing so
I was able to work around the bug. Without doing this I could find no way to
add additional modules to eclipse.
Created attachment 138521 [details]
part of workspace/.metadata/.log with stack trace
(In reply to comment #5)
> I've corrected the screenshot (sorry too quick with the file selection)
> Also, yes I know that one isn't supposed to run eclipse as root, but by doing so
> I was able to work around the bug. Without doing this I could find no way to
> add additional modules to eclipse.
I think I know what's going on here: Extracting the shared libraries after the
build is complete has the side-effect of creating a default configuration. This
configuration has references to all features that were installed when the shared
libraries were extracted, namely all the features in the SDK. In this case there
is a reference to
/usr/share/eclipse/configuration/org.eclipse.update/platform.xml. When you run
Eclipse as root, it is able to write to /usr/share/eclipse/configuration so it
can correct the mis-configuration of
We are planning to get rid of this default configuration in the next update of
Eclipse. Since /usr/share/eclipse/configuration is not writable as a user and
there is no default configuration in /usr/share/eclipse/configure, one would be
created in ~/.eclipse/configuration and this problem would go away.
Thanks for the bug report.
*** Bug 212559 has been marked as a duplicate of this bug. ***
This should be fixed in 3.2.1-24.fc6. Since you ran eclipse as root, you may
have to uninstall eclipse, sudo rm -r /usr/share/eclipse and reinstall eclipse.
If you are still having problems, feel free to re-open this bug.