|Permissions problems in my workspace (self-caused, self-resolved) [message #1759768]
||Tue, 18 April 2017 02:39
| Linus Sch
Registered: April 2017
I've had a rocky install experience with the latest version of Eclipse (Neon.3) onto Linux Mint 17.2 Rafaela. The installer would fail to start with a file permissions error, which I first tried to counter by running the installer with sudo - bad idea! Even though I changed the installation folder to a subfolder of my own home, some files ended up in /root/ and therefore that install would only start when run with sudo.
I am reasonably sure I was able to clean up that mess. For the next try I did chmod 777 on the downloaded and unpacked installer files, so that I could start the installer without sudo. This installation now starts up fine, but it does report some file permissions errors in the terminal I start it from, and upon shutdown I get a dialog box with a file permission error related to saving the workspace.
Doing ls -l on the installation folder, which is in the default ~/eclipse/java-neon/eclipse/ location,
reveals that some of these files are owned by me and some of them are owned by root. Here is the question: is that correct? Or should I just take ownership of the entire installation folder (which I'm 99% sure would get rid of the errors), is that what it should be like? Or, is it at least a safe workaround?
Given the large repositories of many Linux distros I don't have a lot of experience with installing things manually, which might be the problem here. I'm happy to learn
[Updated on: Tue, 18 April 2017 09:08]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03127 seconds