desktop-packages team mailing list archive

[ser <seanerussell@xxxxxxxxx>]

Same error here:

duplicity 0.7.01
gpg (GnuPG) 1.4.18
Ubuntu 15.04
Python 2.7.9

/usr/bin/duplicity incremental \
       # Many --excludes
        --tempdir=/tmp \
        --encrypt-key 09E5788F \
        --use-agent \
        $HOME file://${HOME}/Network/DIMHOLT/Data

eventually results in:

Copying duplicity-full-signatures.20150805T004551Z.sigtar.gpg to local cache.
Attempt 1 failed. IOError: [Errno 5] Input/output error
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: cancelled by user
gpg: encrypted with 2048-bit ELG-E key, ID DCFE3A67, created 2013-07-06
"XXX XXX <XXX@xxxxxxx>"
gpg: public key decryption failed: bad passphrase
gpg: decryption failed: secret key not available
===== End GnuPG log =====

-- 
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/946988

Title:
  GnuPG passphrase error after failed backup session

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Precise:
  Fix Released

Bug description:
  After a failed backup session, duplicity cannot resume the volume
  creation, and seems to fail with "bad passphrase". It is, however, the
  same passphrase that is always used.

  The backup set thus seems to be unusable, and the only solution I've
  found is to simply create a new backup set in a new directory, losing
  incremental history.

  Full output attached as "duplicity-error-incremental-log-v9".

  Also reported as Debian bug #659009, but it has gotten no attention
  for a month.

  Duplicity 0.6.17
  Python 2.7.2+
  Debian Sid
  Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/946988/+subscriptions