I thought I added my experiences with this bug. This might especially
help people who were redirected here by duplicates of this bug.

One day, when I was trying to backup files on a USB HDD, deja-dup would
keep asking for a password and not do anything. The day before, it still
worked (on Arch Linux with deja-dup 22.1 and gnupg 2.0.19). The debug
output was similar, yet different to the one in the bug description.
Essentially, the GPG output was:

gpg decrypt_message failed: unknown system error

It turned out that the backup files created the day before were
corrupted, i.e. 0 bytes. This was most likely due to turning off the USB
disk before its cache was flushed. Deleting the 0-byte files made deja-
dup continue to work again as expected.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/681002

Title:
  gpg: problem with the agent: Bad CA certificate

Status in Déjà Dup Backup Tool:
  Invalid
Status in GNOME keyring services:
  Fix Released
Status in “gnome-keyring” package in Ubuntu:
  Fix Released

Bug description:
  If I don't encrypt the backup all works well, otherwise...

  [...]
  DUPLICITY: INFO 1
  DUPLICITY: . GPG error detail: Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1245, in <module>
  DUPLICITY: .     with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1238, in with_tempdir
  DUPLICITY: .     fn()
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1220, in main
  DUPLICITY: .     incremental_backup(sig_chain)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 488, in incremental_backup
  DUPLICITY: .     globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 295, in write_multivol
  DUPLICITY: .     globals.gpg_profile, globals.volsize)
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 291, in GPGWriteFile
  DUPLICITY: .     file.close()
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 180, in close
  DUPLICITY: .     self.gpg_failed()
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 165, in gpg_failed
  DUPLICITY: .     raise GPGError, msg
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . ===== Begin GnuPG log =====
  DUPLICITY: . gpg: problem with the agent: Bad CA certificate
  DUPLICITY: . ===== End GnuPG log =====
  DUPLICITY: . 
  DUPLICITY: . 

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . ===== Begin GnuPG log =====
  DUPLICITY: . gpg: problem with the agent: Bad CA certificate
  DUPLICITY: . ===== End GnuPG log =====
  DUPLICITY: . 
  [...]

  I'm using duplicity-0.6.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/681002/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to