This bug was fixed in the package duplicity - 0.7.06-2ubuntu3 --------------- duplicity (0.7.06-2ubuntu3) zesty; urgency=medium
* d/p/backport-fix-tags-in-locked-folders.patch: - Fix OSError looking for tag in locked folders with exclude-if-present (LP: #1620085) * d/p/backport-crash-on-restore.patch: - Guard a chown call to avoid a stacktrace (LP: #1642813) * d/p/backport-ignore-excluded-locked-files.patch: - Ignore excluded locked files rather than giving noisy errors (LP: #1089131) * d/p/backport-downgrade-error.patch: - Make locked file messages be warnings not errors, again. This avoids confusing deja-dup. (LP: #1605939) * d/p/backport-flush-after-write.patch: - Flush after writing a temp file, to keep disk in sync (LP: #1538333) * d/p/backport-gpg2.patch: - Improve support for gpg2 (fixing FTBFS in process) -- Michael Terry <mte...@ubuntu.com> Tue, 07 Mar 2017 18:48:01 -0500 ** Changed in: duplicity (Ubuntu Zesty) Status: Triaged => Fix Released -- 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/1605939 Title: Error on locked files causing deja-dup "Backup Failed" Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Zesty: Fix Released Bug description: Deja-dup backups display a pop-up window (likely since 0.7-r1224, 0.8-r1111, 2016-06-13) saying: == BACKUP FAILED Error accessing possibly locked file /etc/.pwd.lock == This is likely an error in duplicity 0.7.08 Running: export DEJA_DUP_DEBUG=1 deja-dup --backup it looks as though the backup is actually completing successfully, but is displaying an error screen. The duplicity command itself can be obtained from the output of the above command: /usr/bin/duplicity --exclude=/tmp/1604_dup --include=/home/aaron/.cache/deja-dup/metadata --include=/etc --exclude=/home/aaron/Downloads --exclude=/home/aaron/.local/share/Trash --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp --exclude=/home/aaron/.xsession-errors --exclude=/home/aaron/.steam/root --exclude=/home/aaron/.Private --exclude=/home/aaron/.adobe/Flash_Player/AssetCache --exclude=/home/aaron/.cache/deja-dup --exclude=/home/aaron/.cache --exclude=/home/aaron/.local/share/Steam --exclude=/home/.ecryptfs/aaron/.Private --exclude=** --gio --dry-run --volsize=50 / file:///tmp/1604_dup --verbosity=9 --gpg-options=--no- use-agent --archive-dir=/home/aaron/.cache/deja-dup --tempdir=/tmp Running this command directly, duplicity appears to run correctly, so this is likely an issue with the duplicity error changing slightly and triggering the "Backup Failed" warning. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1605939/+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