Arch Linux User Repository

Direct download links page: https://support.crashplan.com/hc/en-us/articles/8717685436173#Direct_download_links

@gadicc, I added some pacman hooks to handle setting/unsetting the immutable flag:

Sets immutable flag after install/upgrade:

[Trigger]
Operation = Upgrade
Operation = Install
Type = Package
Target = crashplan-pro

[Action]
Description = Set immutability of Crashplan Pro upgrade directory
When = PostTransaction
Exec = /usr/bin/bash -c "rm -rf /opt/crashplan/upgrade/*; chattr +i /opt/crashplan/upgrade"`

Unsets immutable flag before upgrade/remove:

[Trigger]
Operation = Upgrade
Operation = Remove
Type = Package
Target = crashplan-pro

[Action]
Description = Undo immutability of Crashplan Pro upgrade directory
When = PreTransaction
Exec = /usr/bin/bash -c "chattr -i /opt/crashplan/upgrade"```

I did try the earlier PKGBUILD, but crashplan have removed the older tgz from their server. Also I don't have any issue running the crashplan (java) service. I am seeing the segfault when I start the CrashPlanDesktop electron app.

If any one else still has the older tgz and can share, that would greatly help as well

@gotunandan: You can checkout the git repo for this aur package and then checkout older versions of the PKGBUILD, if you want to try the previous version. Assuming it can still be downloaded at the same url on Crashplan's side of things.

I've got two hosts running the latest version now, they upgraded fine from the previous. I know it doesn't help, but at least you know it should work.

Make sure your java -version is pointed at the right one. Maybe try a re-build and re-install of the package, in case something went wrong? :/

The CrashPlanDesktop app for version 6.8.2 is immediately segfaulting on launch :(

Reading symbols from /opt/crashplan/electron/crashplan...(no debugging symbols found)...done. [New LWP 23456] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `./electron/crashplan'. Program terminated with signal SIGSEGV, Segmentation fault.

0 0x0000000000c39ea0 in ?? ()

(gdb) bt

0 0x0000000000c39ea0 in ()

1 0x00007f2c3ff673a2 in node::http2::Http2Session::Callbacks::Callbacks(bool) () at /opt/crashplan/electron/libnode.so

2 0x00007f2c3ff67465 in () at /opt/crashplan/electron/libnode.so

3 0x00007f2c401c26da in call_init.part () at /lib64/ld-linux-x86-64.so.2

4 0x00007f2c401c27da in _dl_init () at /lib64/ld-linux-x86-64.so.2

5 0x00007f2c401b403a in _dl_start_user () at /lib64/ld-linux-x86-64.so.2

6 0x0000000000000001 in ()

7 0x00007ffc06d1124d in ()

8 0x0000000000000000 in ()

I cannot revert back to 6.7.x either as their 'Downloads' page no longer lists that version. I tried downloading the earlier PKGBUILD but found that the earlier version has apparently been removed from their server too.

I'm stuck with a 'paused' backup that will not resume from their web administration console either :( I've created support ticket with code42 about this, but any help here would be appreciated too

Looks like the new version has a gtk3 dependency.

I swear I was a co-maintainer for this AUR package, but I guess not. Have a PKGBUILD all ready to go, but can't push it. :(

@evantatarka put this URL in the out-of-date flag: https://web-eam-msp.crashplanpro.com/client/installers/CrashPlanSmb_6.8.2_1525200006682_369_Linux.tgz

You can download the snapshot and change the first part of PKGBUILD to this one:

pkgname=crashplan-pro

pkgname=crashplan pkgver=6.8.2 _pkgtimestamp=1525200006682 _pkgbuild=369 pkgrel=1 pkgdesc="An business online/offsite backup solution" url="http://www.crashplan.com/business" arch=('x86_64') license=('custom') depends=('bash' 'java-runtime-headless=8' 'alsa-lib' 'gconf' 'gtk2' 'libxss') makedepends=('cpio') conflicts=('crashplan') install=crashplan-pro.install source=(https://web-lbm-msp.crashplanpro.com/client/installers/CrashPlanSmb_${pkgver}${pkgtimestamp}${_pkgbuild}_Linux.tgz crashplan-pro crashplan-pro.service) sha256sums=('54b7c0cdde1db0dc3dbfd76445574119b84a9cfa6eec81054b55ab4f11c29a16' 'b306d7da0dd41341512ce80ddcfb21bff8a9bb73ab5018696e69d08b89f7f1b6' 'fd4c80dbd2ea3dcfc9966832a599f1bb310f705f813474d1900c1867ea55155c')

It looks like there's a new upgrade getting pushed again. Mine started attempting to auto-update around 2018-08-21 14:57 (CDT). I can't grab the new URL right now though.

@ZimbiX you might consider overriding the crashplan-pro.service unit and use ExecStartPre= to delete the files in /opt/crashplan/upgrade each time the service is started.

I considered adding such to the package but I thought it seemed a bit unorthodox? I'm open to feedback from the community on this.

@ZimbiX I think that's going to be a problem as long as we CrashPlan continues to take their auto-upgrade approach. I think the general approach to counteract it today is:

1. Clean out the upgrade packages and logs to get filesystem capacity back
2. Upgrade to the latest package from AUR
3. Start your backups again

#2 has been much more easy and reliable since the AUR package has been staying up-to-date since aaronm-cloudtek took over as the maintainer.

If this isn't good enough, you could always write and run a script that monitors whether it's trying to auto-apply a new upgrade and if so, stop the service before it downloads upgrade packages indefinitely until it files your filesystem. Then you could intervene with the new AUR package upgrade a little more easily.