Please upgrade to the current version of duplicity. If you can reliably reproduce this bug, please let me know what you did, in detail, with attached -v9 log files and minimal munging. DO NOT copy/paste log files here. They are impossible to read.
I took the script in the bug description section, modified it to use verify instead of the check kludge, and have been unable to reproduce it after many runs. It still fails to verify this bug. There are multiple options both stable and latest: - Stable snap builds - “sudo snap install duplicity —classic" - Latest snap builds - “sudo snap install duplicity —classic —edge" - Stable pip3 builds - “sudo pip3 install duplicity" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git - Latest duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git - Stable tarball install - https://launchpad.net/duplicity/+download - Source - https://gitlab.com/duplicity/duplicity Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. ** Changed in: duplicity Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" Status in Déjà Dup: Invalid Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Lucid: Fix Released Status in duplicity source package in Maverick: Won't Fix Status in duplicity source package in Natty: Fix Released Bug description: When restoring a backup, one might see an error like: Invalid data - SHA1 hash mismatch: Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9 Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2 This can happen when a volume file was not completely written to the backend before duplicity was interrupted (say, shutting down the machine or whatever). When duplicity resumes the backup next run, it will start with the next volume. The half-complete volume file will sit on the backend and cause this error later when restoring. You can manually recover from this by either restoring from your older backup sets or by restoring individual files that don't happen to be in the corrupted volume. == To Reproduce == See attachment https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh for a test script tor reproduce the problem. == Ubuntu SRU Justification == This is a serious data loss problem for users, which won't be noticed until they try to restore. With Ubuntu 11.10 including Deja Dup, some users may think to back up their data first then upgrade, and may accidentally create corrupted backups. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
