Déjà Dup

  1. Bug #681002
  2. Comment #29

Comment 29 for bug 681002

Revision history for this message
echo777 (echo777) wrote :

I can reproduce Ross Gayler's problems:

DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1412, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1405, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1281, in main
DUPLICITY: . sync_archive(decrypt)
DUPLICITY: . File "/usr/bin/duplicity", line 1081, in sync_archive
DUPLICITY: . copy_to_local(fn)
DUPLICITY: . File "/usr/bin/duplicity", line 1028, in copy_to_local
DUPLICITY: . gpg.GzipWriteFile(src_iter, tdp.name, size=sys.maxint)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 371, in GzipWriteFile
DUPLICITY: . new_block = block_iter.next()
DUPLICITY: . File "/usr/bin/duplicity", line 1008, in next
DUPLICITY: . self.fileobj.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 225, in close
DUPLICITY: . assert not self.fileobj.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 239, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 206, in gpg_failed
DUPLICITY: . raise GPGError, msg
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . ===== Begin GnuPG log =====
DUPLICITY: . gpg: CAST5 encrypted data
DUPLICITY: . gpg: encrypted with 1 passphrase
DUPLICITY: . gpg: decryption failed: bad key
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .
DUPLICITY: .

DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . ===== Begin GnuPG log =====
DUPLICITY: . gpg: CAST5 encrypted data
DUPLICITY: . gpg: encrypted with 1 passphrase
DUPLICITY: . gpg: decryption failed: bad key
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .

I must have canceled a backup during one of its runs. Now it doesn't accept my password, even though they have been saved previously and used for over a month. Has this issue ever been solved?