Menu

#597 Unhelpful feedback "No valid JRE found in /usr/java."

areca-7.x
open
nobody
None
1
2017-10-29
2016-04-08
No

Starting areca.sh with sudo results in failure with No valid JRE found in /usr/java. which is unhelpful because it doesn't explain why /usr/java is accessed in the first place (must be due to an environment variable or configuration parameter, so add it to the output).

Discussion

  • Kalle Richter

    Kalle Richter - 2016-04-08

    experienced with 7.5 on Ubuntu 16.04

     
  • Joe Linux

    Joe Linux - 2017-04-22

    Hey, guys,

    this bug is already being discussed here: https://sourceforge.net/p/areca/bugs/581/. Maybe you would want to follow on on that older thread?

    This is a really bad bug because it keeps people from compiling and testing Areca Backup. Please see the discussion here, too: https://forum.mxlinux.org/viewtopic.php?f=121&t=42039. As you can see, it even keeps Areca Backup from being regarded as a candidate for a superb distro's test repo.

    Maybe one of you would be able to provide a clean fix for this? That would be great, and maybe that would help to revitalise Areca Backup, which has great features that are rarely found otherwise.

    I would do it if I could but unfortunately my knowledge is far too limited.

    Greetings, Joe

     
  • steve donato

    steve donato - 2017-10-29

    '/usr/java': No such file or directory and because Ubuntu based linux (and linux mint) put the java directory in /usr/lib not /usr. then after copying java directory to /usr you get this 'No valid JRE found in /usr/java'? Also (trivial but stilll wrong) the linux how to launch linux arceda from the command line instruction incorrectly tells you to use a windows program on linux;
    Use "./bin/run_tui.exe" for the command-line interface\

     

    Last edit: steve donato 2017-10-29
  • steve donato

    steve donato - 2017-10-29

    install instructions also give the following errors; (Linux Mint 18 (ubuntu based 16.4)
    sudo chmod a+x -v bin/*
    mode of 'bin/areca_cl.sh' retained as 0755 (rwxr-xr-x)
    mode of 'bin/areca_decrypt.sh' retained as 0755 (rwxr-xr-x)
    mode of 'bin/areca_dezip.sh' retained as 0755 (rwxr-xr-x)
    mode of 'bin/areca_run.sh' retained as 0755 (rwxr-xr-x)
    mode of 'bin/run_tui.sh' retained as 0755 (rwxr-xr-x)
    so when you try to run after fixing the directory location you get the following
    sudo sh areca.sh
    [sudo] password for steve:
    areca.sh: 1: areca.sh: /usr/lib: Permission denied
    areca.sh: 9: areca.sh: /bin/areca_run.sh: not found
    Nothing was ver put in /bin/ during the install?

     

Log in to post a comment.