Deja Dup thinks rclone.conf is encrypted

I’ve been trying to use rclone with deja-dup and have seen no similar issue anywhere. It’s from the Ubuntu questing repos (49.0), but haven’t seen anything regarding this in .1/.2 changelogs, also haven’t tried the flatpak, but the issue is very strange.

Isn’t deja-dup just checking ~/.config/rclone/rclone.config? I have also tried to encrypt the config and use that password but without success. Is there something I can try or may it be a bug of this specific version?

Thanks in advance!

Update:

Just checked both BackendRclone.vala and Rclone.vala from gitlab.gnome.org and no change has ever been made. Whatever is causing this bug I think is still there.

Update 2:

Problem found. This is an Ubuntu-specific problem (at least on 25.10) that exists because the shipped rclone version is a little old (1.60). Deja-dup verifies the encrypted config by running

rclone config encryption remove

The encryption command does not exist on that rclone. However the biggest problem I think is that installing rclone via Snap/official .sh triggers the rclone missing package since it verifies that rclone is among the installed system packages instead of (more simply imo) verifying if /usr/bin/rclone exists or if which rclone returns.

Will open an issue

Solution: Install Rclone from Rclone downloads as a .deb file

1 Like