I’ve installed DejaDup via Flatpak and have been using it for a few years to successfully make backups; after installing the latest Flatpak (version 47.0, commit bf253158092d38e98151c0c0d458aeb01dd59c1576b9ec40e45fecbcb791481e), every time it tries to make a backup, it just presents an error message that says “Could not understand duplicity version”.
Rolling back to the previous release, dc5cc7a2dcfa43eae22dfc2ef1fc09af7d27a0192cc05e2ad15aac4bffc99614, seems to work around the problem.
Thankfully(?) I can’t reproduce, and this is the first report I’ve seen since releasing 47 a couple weeks ago - so I don’t think the flatpak is entirely broken.
But also, it’s very strange that there would be differences! The flatpak ships its own duplicity … so … why would there be a problem…
Can you run this command and paste the output?
flatpak run --command=duplicity org.gnome.DejaDup --version
So… I just updated to the latest version again, and now it’s working! Just for reference, the output of that command is:
duplicity 3.0.2 August 09, 2024
I haven’t been able to reproduce the previous error I was having, which is good, but I’m not sure how it would have gotten into a bad state in the first place.
Ok, here’s something interesting – today, my automated backup failed, and when I opened up DejaDup, I see the “Could not understand duplicity version” error message again. I get that error message immediately if I click “Back Up Now”, and if I switch to the Restore tab, it’s completely blank.
The weird thing is that I still see a valid version on the command line:
$ flatpak run --command=duplicity org.gnome.DejaDup --version
duplicity 3.0.2 August 09, 2024
I haven’t touched it since I reinstalled it a few days ago; the About Backups dialog says it’s version 47.0, and that matches the version reported by flatpak info org.gnome.DejaDup, so I’m not sure why it’s suddenly failing.