gpg: problem with the agent: Bad CA certificate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Invalid
|
High
|
Unassigned | ||
GNOME Keyring |
Fix Released
|
Medium
|
|||
gnome-keyring (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
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: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/
DUPLICITY: . incremental_
DUPLICITY: . File "/usr/bin/
DUPLICITY: . globals.backend)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . globals.
DUPLICITY: . File "/usr/lib64/
DUPLICITY: . file.close()
DUPLICITY: . File "/usr/lib64/
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File "/usr/lib64/
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
Changed in deja-dup: | |
importance: | Undecided → High |
summary: |
- wrong passphrase during backup (not restore) + gpg: problem with the agent: Bad CA certificate |
Changed in deja-dup: | |
status: | Incomplete → Confirmed |
Changed in deja-dup: | |
status: | Fix Committed → Fix Released |
Changed in deja-dup: | |
status: | Triaged → Invalid |
Changed in gnome-keyring: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
I forgot to say... "wrong passphrase" is the message deja-dup shows in the gui