After upgrading from Fedora 20 to 21, I discovered that Areca no longer starts. Apparently, this is due to the different strings with which OpenJDK identifies itself when running java -version.
OpenJDK 7 in Fedora 20:
java version "1.7.0_71"
OpenJDK Runtime Environment (fedora-2.5.3.0.fc20-i386 u71-b14)
OpenJDK Client VM (build 24.65-b04, mixed mode, sharing)
OpenJDK 8 in Fedora 21:
openjdk version "1.8.0_25"
OpenJDK Runtime Environment (build 1.8.0_25-b18)
OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode)
As far as I can tell, the problem is caused by check_version() in areca_run.sh checking if the first line of the above output starts with "java". Replacing
if [ "$JAVA_IMPL" = "java" ] ; then
with
if [[ "$JAVA_IMPL" = "java" || "$JAVA_IMPL" = "openjdk" ]] ; then
worked around this issue for me.
I can confirm, what user Simpleton said. I tried Areca under Fedora 21 for the first time and got the output
"ls: Zugriff auf /usr/java nicht möglich: Datei oder Verzeichnis nicht gefunden
No valid JRE found in /usr/java."
Then I changed the line in /areca/bin/areca_run.sh like user Simpleton pointed out ... and then Areca starts fine.
Same here on archlinux 64bit.
Same here on Fedora 22.
But in my opinon, the proposed solution is not correct. OpenJDK, reports the version as openjdk version "1.8.0_51". So the sed command does not work and the version check is useless.
For OpenJDK, the following will work correctly.
Simpleton's fix worked for me in Linux Mint/KDE. I had to make a symlink from /usr/lib/jvm/java-9-openjdk-amd64 to /usr/Java.
Lane
I found this replacement file solve the problem https://gist.github.com/JesterEE/1658b83fe3536d6e06a0.
But I'm really disappointed that this bug was not solved since 2015. I began to think that areca is dead with no recent development.