Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to get eclipse 3.8 installed on Ubuntu 10.04. I've put the extracted files on:


I put a symbolic link in:


ls -s /usr/local/bin:

eclipse -> /opt/eclipse/eclipse

My path has /usr/local/bin in it...the permissions for the sym link are 777.

I also did as su:

chmod 755 /opt/eclipse/eclipse

When I try to run eclipse as root, it works ( at least it tries, getting java error ). Trying as regular user just gives me the prompt that I need to install eclipse-platform from the repo.

share|improve this question
I changed the permission on the /opt/eclipse dir from 754 to 755 which now gives a different error when trying to start eclipse as regular user: cannot open shared object file: No such file or directory Eclipse:eclipse The Eclipse executable launcher was unable to locate its companion shared library. The Eclipse executable launcher was unable to locate its companion shared library. – wbg Jun 2 '13 at 3:44
It appears there's an environment variable and I'm working on this via ssh without X11 working. – wbg Jun 2 '13 at 6:19
I think I solved my issue by setting the permissions on the eclipse parent and the env variable which tells eclipse where the it's root dir is. I can't confirm until I try locally. Thank JMG for the edits. – wbg Jun 2 '13 at 16:29
Remember to post your solution as an answer and accepted if you've solved it. – terdon Jun 3 '13 at 14:28

What makes you think it is in your $PATH? Try running echo $PATH, do you see /usr/local/bin?

If you are running this through an ssh session my guess is that you have added /usr/local/bin to your $PATH in your ~/.bahsrc and that is not read when you ssh into a machine. Try adding this to your ~/.profile instead:

share|improve this answer
It seems I might have solved my problem as noted in my comments to my question. I'll check it out in person first. I did echo $PATH originally. Thanks for your thoughts. – wbg Jun 2 '13 at 16:28
@wbg great! Do remember to post it as an answer if you've found it. Also, I just realized I'd made a mistake in my answer. It is ~/.bashrc that is not read when you ssh and ~/.profile that is. My guess is that you were setting your PATH in ~/.bashrc and that's why it wasn't working. This won't be the case if you're opening a terminal locally though. – terdon Jul 4 '14 at 14:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .