Arch Linux User Repository

@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"```

Thanks for fixing and picking up the package legodfrey! Works fine now.

Works for me too! Thanks a lot

It works! Thanks

I managed to get the latest version to work, without completely removing and reinstalling it.

I had to do the standard PKGBUILD update of version and build number, but I also had to disable symbol stripping (options flag in excerpt). so the top of the PKGBUILD now has the following lines

pkgname=crashplan-pro
_pkgname=crashplan
pkgver=7.7.0
_pkgtimestamp=1525200006770
_pkgbuild=833
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' 'gtk3' 'libxss')
makedepends=('cpio')
conflicts=('crashplan')
install=crashplan-pro.install
source=(https://download.code42.com/installs/agent/cloud/${pkgver}/${_pkgbuild}/install/CrashPlanSmb_${pkgver}_${_pkgtimestamp}_${_pkgbuild}_Linux.tgz
        crashplan-pro
        crashplan-pro.service)
sha256sums=('f105feaa533661041194bd1eb154475e220d30db40cf4764a8662b55d14d14bf'
            'b306d7da0dd41341512ce80ddcfb21bff8a9bb73ab5018696e69d08b89f7f1b6'
            'fd4c80dbd2ea3dcfc9966832a599f1bb310f705f813474d1900c1867ea55155c')
options=(debug !strip)

If someone else wants to try and see if this fixes the problem of Crashplan sitting there claiming to be running then that would be great!

If this works then I will adopt and update the package, (I made other changes to my system while making this fix work, so I want someone to say this was the required change).

I see there are quite a few struggling here with CrashPlan and I just want to reiterate that it works fantastically with the simple systemd service I described below.

There are no kernel incompatibilities, or any other significant issues with CrashPlan and Arch. I'm running it on two Arch systems right now with kernel 5.5.4, and after reading these comments I also tried it on 5.4.20 and it works just as well. And as I said, my archives are around 10TB.

I think the problem is not only this AUR package itself, but also that it can be difficult to uninstall. In fact after initially using this package I had to reinstall Arch because I just couldn't get CrashPlan to work after this package was installed and uninstalled.

In any case, I wish all of you the best of luck, and urge you to try the systemd method. If CrashPlan still doesn't work then you may have to reinstall Arch.

I also had a quick support back and forth with the CrashPlan helpdesk. Just confirming what the rest of you said. They can't provide help for Arch since they don't officially support it.

I installed Ubuntu 18.04 (they don't officially support 19.10 either) in a VM and the latest CrashPlan works fine there. Installing it in a 18.04 Docker container however results in the same issue we see on Arch, so I also figured it's probably an incompatibility with the Kernel. Can't say for sure though.

Regardless, all we can do is wait or run it in a VM, which seems kinda wasteful and would require migrating the backups, which is a pain.

I tried to downgrade to kernel 4.19.x: The Desktop app don't even start, the service is active but nothing is done. I don't think the problem is kernel...

I just contacted crashplan support about the gui not being able to connect to the running service. They said they are aware of the problem and think it has to do with some recent change in the linux kernel. As they don't support Arch Linux they couldn't help me further. I tried downgrading as far back as 5.4.15 just to check but that didn't resolve it for me.

I installed 7.7.0 by changing to pkgbuild and get the same problem as achilleas.k and blackhole: service seems to be running but not do anything, and the front end cannot connect to the running service.

I'd pick it up but I've been honestly considering switching to another service (maybe Backblaze B2). If I decide I'm too lazy to migrate and no one picks it up soon, I'll grab it.