-
Notifications
You must be signed in to change notification settings - Fork 132
Cannot install Sloeber V4.4.1 on Linux #1557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For safety reasons all osses are defaulting to as little as possible read/write acess. This causes plenty of issues for software installation. arduino-eclipse-plugin/io.sloeber.core/src/io/sloeber/core/tools/PackageManager.java Line 336 in 0076c52
Which seems to fail due to the os not entitling Sloeber to do so. Note that Sloeber allows for setting the SLOEBER_HOME environment variable. In that case the Sloeber install folder will be ${SLOEBER_HOME}/arduinoPlugin I hope this helps |
I just ran into the same issue. It appears from my initial look that the issue is with the JRE file: |
Maybe a chmod -R plugins/org.eclipse.justj.openjdk.hotspot.jre.full.linux.x86_64_*/jre should be a better way. What do you think? |
That should work... I just confirmed a fresh install with
Just to make sure no typos I copied and pasted from the window I used. |
Thank You very much. |
I'm not sure what you are referring to but mostly when people say "parameters changed in Sloeber" they actually installed a different platform version. |
Yes, that is true. For a short test I used the latest versions of Arduino tools and in my projects I seldom change the tool version. |
Same problem here. I would strongly urge the developers to distribute this as a compressed tar archive in the future. This problem then becomes a complete non-issue because tar (short for tape archiver) properly restores directory/file permissions and ownership, hard/soft links, sockets, etc. Linux users will certainly know how to use tar, so it becomes a simple untar, and run situation. Yes, ZIP is more portable but it's totally not required here (as nobody installs the Linux version on MacOS or Windows). I determined the specific permission fixes required by looking at the executable files in the Debian (Bullseye 11.6) packaged version of JDK/JRE 17. Here is a work-around I tested (and it worked perfectly for me);
|
@jantje 7zip application on Windows also knowns tar archive :) |
@uzi18 We tried with tar an 7zip. |
This is fixed in the pull request that I just made. (Changed package format on Linux from |
I have 2 PCs (64 Bit) running Sloeber V4.4.0 without problems: Linus Mint (Targa, based on Ubuntu 18.04) and Ubuntu 20.04.
Now I want to Update to version 4.4.1.
I downloaded 64 Bits Bundle from http://eclipse.baeyens.it/stable.php?OS=Linux and de-zipped it in a folder Sloeber in my home directory.
I followed the steps given with the latest version.
Then I started sloeber-ide (via double mouse click in file manager, the same behavior via terminal) and a pop-up-window reports:
Then I started
Everything seems OK, Eclipse/Sloeber starts and begins downloading and installing resources. But then it stops with the following error in a small Pop-up:
The click on Error Log gives the following information (copied lines to text editor):
It is a pity, that my know-how is to less to have any idea for solving this problem.
It seems, that Java 11 is required and Java 17 is used. But I thought, that having Eclipse/Sloeber with the Bundle-Installation just is made for avoiding such problems. And why does 4.4.0 run, but not 4.4.1?
At the time I have to continue with version 4.4.0.
I just try to install remote debugging (and compiling) on Raspberry Pi (3 B and 4 B) with my Eclipse/Sloeber and for this I wanted to use the latest version. I have that Raspberry Pi remote debugging already running with Eclipse CDT 2022-12 (which may be the reason for using Java 17) and wanted to test step by step, if it is possible with Sloeber. But now I think it is more import to have version 4.4.1 running at all.
The text was updated successfully, but these errors were encountered: