Package Details: areca 7.5-2

Git Clone URL: (read-only, click to copy)
Package Base: areca
Description: Personal file backup software supporting compression, encryption and incremental backups.
Upstream URL:
Keywords: backup gui incremental java
Licenses: GPL2
Submitter: fi-dschi
Maintainer: SanskritFritz (shimi)
Last Packager: SanskritFritz
Votes: 51
Popularity: 0.000000
First Submitted: 2007-11-05 12:28 (UTC)
Last Updated: 2016-02-10 15:04 (UTC)

Dependencies (3)

Required by (0)

Sources (6)

Latest Comments

SanskritFritz commented on 2020-03-01 09:40 (UTC)

@Telavus I actually don't recommend to use Areca at the moment, it seems abandoned for years now. I liked it too, but switched to Borg backup some time ago and this is what I recommend to you as well.

Telavus commented on 2020-03-01 03:21 (UTC)

Anyone know how to deal with this?

/areca/src/build.xml:102: The following error occurred while executing this line: /areca/src/build.xml:82: Warning: Could not find file /areca/src/jni/ to copy.

Customizer commented on 2017-05-28 16:00 (UTC)

export SWT_GTK3=0 indeed helps, but I don't understand why. Can anyone explain the root cause of the problem? Development of areca seems pretty much abandoned to me, but perhaps they will release a new version if we provided a patch, which fixes the underlying problem.

DevotedFollower commented on 2017-04-10 16:47 (UTC)

Hi stef204, if the problem you are describing is that the areca gui suddenly crashes when you click on a "target" (left hand side of the screen) to start a backup. Then edit your file to have the following line in it: export SWT_GTK3=0 hope this helps, DF

stef204 commented on 2017-04-08 01:25 (UTC) (edited on 2017-04-08 09:45 (UTC) by stef204)

This package crashes as soon as I try to save a Target. OTOH, the areca-bin package, seems to run fine (both packages with the jdk fix in This may not be an upstream bug since the binary works fine. It may be an "Arch" issue, a build issue (how the PKGBUILD compiles it) or simply some quirk on my box. Anyone else here with same issue and if so, any fixes? % archlinux-java status Available Java environments: java-7-openjdk java-8-openjdk (default) # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fe5fabc9b2c, pid=6244, tid=0x00007fe69d27a700 # # JRE version: OpenJDK Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13) # Java VM: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [] gdk_display_open+0x5c # # Core dump written. Default location: /home/$(user)/core or core.6244 # # An error report file with more information is saved as: # /home/$(user)/hs_err_pid6244.log # # /opt/areca/bin/ line 114: 6244 Aborted (core dumped) "${JAVA_PROGRAM_DIR}java" -Xmx1024m -Xms64m -cp "${CLASSPATH}" -Duser.dir="${PROGRAM_DIR}" -Djava.library.path="${LIBRARY_PATH}" $1 "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9" "${10}" "${11}" "${12}" I've got the coredump from areca, Do you want to see it? Or better to just contact upstream?

SanskritFritz commented on 2016-08-04 07:43 (UTC)

This is a bug, simple as that. But thanks for the workaround, that works well.

jerome2016 commented on 2016-08-04 02:36 (UTC) (edited on 2016-08-04 02:47 (UTC) by jerome2016)

i have a dialogBox that open and ask for a contribution (use more than 31 times). Ok... but the link on the dialogBox doesn't works and this freeze areca (can not close it more... need to xkill or killl process). The only one way i find is to xkill the contribution dialogBox windows, then still can use areca. So, i think: 1/ the call for contribution failed 2/ Arcea is it free, or a trial software. If it is a non free software, it should be fine to tell it clearly. thank you very much

DevotedFollower commented on 2015-08-16 17:23 (UTC)

thanks SanskritFritz, here's the page regarding areca and problems launching with openjdk8: Hopefully something gets done about it, but in the meantime you can edit your /opt/areca/bin/ file as mentioned. hope this helps, DF

SanskritFritz commented on 2015-04-08 19:39 (UTC)

That file is coming from upstream, please contact Olivier about this on sourceforge.

ifelseforeach commented on 2015-04-08 18:29 (UTC)

The script /opt/areca/bin/ throws: 'No valid JRE found in /usr/java' This is caused by the versioncheck in line 69. Can be fixed by replacing the if with this if: if [[ "$JAVA_IMPL" = "java" || "$JAVA_IMPL" = "openjdk" ]] ; then

SanskritFritz commented on 2015-03-08 15:23 (UTC)

shimi, you're right, I just checked it. The areca-bin package is the one which doesn't need swt, since it contains it, but this one needs it. Thanks for the heads-up.

shimi commented on 2015-03-08 15:12 (UTC)

For me Areca only runs if swt is installed. Removing the swt package causes this error when trying to run areca: Installing swt makes it run fine.

SanskritFritz commented on 2014-11-10 21:21 (UTC)

I'm sure, Areca works without external swt libs.

LeCrayonVert commented on 2014-11-10 21:18 (UTC)

Are you sure 'swt' should be put in makedepends ? I would put it in depends instead

SanskritFritz commented on 2014-10-17 19:44 (UTC)

Thank you.

ozwigh commented on 2014-10-17 19:38 (UTC)

jre7-openjdk 7.u71_2.5.3-1 introduces new bug (misfeature) to CipherInputStream which causes javax.crypto.BadPaddingException. Bug is reported upstream, while waiting for workaround downgrade to jre7-openjdk 7.u65_2.5.2-3 solves problem.

SanskritFritz commented on 2014-06-20 21:18 (UTC)

New version of areca and the package is compiled from source now. That means, two new dependencies are needed for the build. The old style binary package lives on as areca-bin.

SanskritFritz commented on 2014-06-13 07:43 (UTC)

Mikaye, good point, I'll look into that. Maybe we could have two packages, areca compiled from source, and this one transferred to areca-bin?

Mikaye commented on 2014-06-12 18:55 (UTC)

Please don't use precompilated binaries since it can't be built on other architectures than i686 or x86_64 (Archlinux ARM for example)

SanskritFritz commented on 2013-10-22 12:48 (UTC)

This is no support forum, please try it upstream: or

hal commented on 2013-10-22 12:25 (UTC)

Hello! Areca stopped to work a few feeks ago. I'm not even sure this is an areca bug. Here is the terminal output (during when areca running): (SWT:849): GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed (SWT:849): GLib-GObject-WARNING **: gclosure.c:697: unable to remove uninstalled invalidation notifier: 0x7fed5c400100 (0x7fed60903f20) And then at some point (trying to setup a new target) areca quits with the following message. (SWT:849): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fed5c3f9a48, pid=849, tid=140657659537152 # # JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/hal/hs_err_pid849.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # /opt/areca/bin/ line 98: 849 Aborted (core dumped) "${JAVA_PROGRAM_DIR}java" -Xmx256m -Xms64m -cp "${CLASSPATH}" -Duser.dir="${PROGRAM_DIR}" -Djava.library.path="${LIBRARY_PATH}" $1 "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9" "${10}" "${11}" "${12}"

SanskritFritz commented on 2011-12-23 19:32 (UTC)

Thanks clickit for your help.

clickit commented on 2011-12-23 17:38 (UTC)

yes, it worked now thx

SanskritFritz commented on 2011-12-23 12:16 (UTC)

Done, would you please test.

SanskritFritz commented on 2011-12-23 11:22 (UTC)

Oops, you're right, I forgot that there are 32 and 64 bit versions separate. Hang on, as soon I'll have some time, I'll correct this.

clickit commented on 2011-12-23 06:40 (UTC)

I had this error when updating areca 7.2.1-1 -> 7.2.4-1: Validating source files with md5sums... areca-7.2.4-linux-gtk-32.tar.gz ... FAILED ... Passed ... Passed ... Passed ... Passed areca.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build areca. solution: edit PKGBUILD and replace with the correct mdsum value -> eef3d5b66ceb9070e9d22485401c413f for areca-7.2.4-linux-gtk-32.tar.gz file

SanskritFritz commented on 2011-12-22 01:20 (UTC)

Can anyone please test if the areca.desktop file also works if Oracle JRE is installed?

SanskritFritz commented on 2011-02-23 22:37 (UTC)

Thanks, fi-dschi, this way it works. I tested the basic functions, all seem to work. Do you think I should report that issue upstream?

fi-dschi commented on 2011-02-23 22:18 (UTC)

Reboot your system. Afterwards, try to execute > java -version from the command line. As long as that's not working you will have to look for a fix for that problem (binary "java" not found by system). This workaround might help for Areca: Set JAVA_PROGRAM_DIR=/usr/bin/ in the options section of /opt/areca/bin/

SanskritFritz commented on 2011-02-23 21:39 (UTC)

This package doesnt work with OpenJDK (64 bit). Is this Areca's fault or is there something I can do in the PKGBUILD? ~> areca ls: cannot access /usr/java: No such file or directory No valid JRE found in /usr/java.

fi-dschi commented on 2011-02-23 18:35 (UTC)

For release notes visit

fi-dschi commented on 2010-10-20 21:10 (UTC)

Version numbers are now correct

LeCrayonVert commented on 2010-10-02 15:59 (UTC)

About dialog still shows 7.1.7 as the latest version. Maybe it's because areca official web site has not been updated yet.