When using "Backups" (a.k.a. deja-dup) - it doesn't find duplicity, although it's installed:

I have been trying to backup using "Backups" (a.k.a. deja-dup), and it turns out that the current duplicity (which deja-dup uses) still has the "Unicode bug" (it fails when dealing with Unicode strings). (I have "Backups" (a.k.a. deja-dup) installed on my system: "deja-dup backup tool" v 37.0, and had duplicity v 0.7.17).

My system:

~$ lsb_release -a
Description:   Ubuntu 18.04.3 LTS; Release:  18.04; Codename:   bionic

So, I then removed the existing installation of duplicity, and installed duplicity 0.8 from source: https://launchpad.net/duplicity. It installs duplicity at: /usr/local/bin. It's in PATH:

~$ echo $PATH

After loading and installing all the requirements, duplicity 0.8 itself runs fine:

~$ duplicity -V
duplicity 0.8.05

But, when running "Backups" (deja-dup), it doesn't find it. A window pops up, saying:


In order to continue, the following package needs to be installed: duplicity

I installed dconf-editor, found /org/gnome/deja-dup, but I don't see there any settings for the duplicity path.

nautilus and "apt list --installed" don't see it, either.

Note: cross posted here

  • Cross posting is discouraged on the SE network: meta.stackexchange.com/questions/64068/…
    – Haxiel
    Oct 10, 2019 at 11:35
  • Where does deja-dup search for duplicity? AFAIK the standard installation path is /usr/bin/duplicity, so set a symlink there. I assume deja-dup uses absolute paths for commands.
    – FelixJN
    Oct 31, 2019 at 16:10

1 Answer 1


deja-dup does not look for the duplicity binaries but looks at the installed packages.

Try to recompile deja-dup without HAS-PACKAGEKIT defines. This can be done by commenting out these lines in meson.build

#if packagekit_dep.found()
#common_vflags += ['--define=HAS_PACKAGEKIT']

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .