Déjà Dup

gpg: problem with the agent: Not implemented

Bug #792556 reported by Alexandre Demers on 2011-06-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Déjà Dup	Fix Released	High	Unassigned	Déjà Dup 19.3 "3.1.3"

Bug Description

Using Gnome 3, gnupg 1.4.11 and gnupg2 2.0.14, duplicity 0.6.13 and deja-dup 18.1.1 on Ubuntu 11.04 64 bit. When selecting to encrypt backup, Deja Dup always fails saying Bad encryption password. Launching deja-dup with debug shows the following:
DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1262, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1255, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1228, in main
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File "/usr/bin/duplicity", line 417, in full_backup
DUPLICITY: . globals.backend)
DUPLICITY: . File "/usr/bin/duplicity", line 295, in write_multivol
DUPLICITY: . globals.gpg_profile, globals.volsize)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 291, in GPGWriteFile
DUPLICITY: . file.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 180, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File "/usr/lib/python2.7/dist-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: Not implemented
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: Not implemented
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .

DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /home/dema1701/.cache/deja-dup/2b989032691259a82d5345e67ca8897f/duplicity-j8G_RS-tempdir/mktemp-akPCay-1

DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /home/dema1701/.cache/deja-dup/2b989032691259a82d5345e67ca8897f/duplicity-52isP1-tempdir/mktemp-3P19J7-1

Related branches

lp://staging/~deja-dup-team/deja-dup/20

Revision history for this message

Michael Terry (mterry) wrote on 2011-06-16:

This was a problem on Fedora 13 a while ago. Something to do with seahorse-plugins. https://bugzilla.redhat.com/show_bug.cgi?id=622358

This also sounds similar to bug 681002 because it relates to problems with the gpg agent. That bug lists killing gnome-keyring-daemon as a workaround. Does that help?

Changed in deja-dup:
importance:	Undecided → High
status:	New → Incomplete
summary:	- Can't use encryption + gpg: problem with the agent: Not implemented

Revision history for this message

Alexandre Demers (oxalin) wrote on 2011-06-16:

Indeed, killing gnome-keyring-daemon does do the trick. So it's more like 681002 than 622358.

Michael Terry (mterry) on 2011-06-16

Changed in deja-dup:
status:	Incomplete → New

Revision history for this message

Michael Terry (mterry) wrote on 2011-06-16:

OK, I think I fixed this. Basically, Deja Dup never needs to use a gpg agent, and using an agent isn't even enabled in gpg by default normally. But it is enable as a global default on (at least) Ubuntu.

I'm not sure why sometimes the agent likes to complain about something being not implemented, but regardless. I've now made Deja Dup pass the --no-use-agent flag to gpg. That will avoid this point of failure in the future.