GnuPG: problem with the agent: Bad CA certificate

[Genetic]

Hi,

I have a problem with duplicity or gpg, I'm not sure:

Code: Select all

me@Home ~/downloads % PASSPHRASE=blubb duplicity ~/bin file:///home/me/downloads/backup/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: problem with the agent: Bad CA certificate
===== End GnuPG log =====

The thing is, it worked until some days ago, but I don't know which update caused the problem. Sorry for the rather vague question, but maybe someone can give me a hint what's actually going wrong and/or how to solve the problem?

Thanks in advance
Genetic

[Genetic]

gnome-keyring-daemon seems to be the culprit. Killing that process (or configuring gnome not to start it in the first place) prevents the error.

[lexming]

Just encountered this problem with deja-dup (a front-end for duplicity). I solved it, or workaround it, by disabling in gnome-session the launch of the gnome keyring GPG service, not the whole gnome-keyring-daemon:

Code: Select all

gnome-keyring-daemon --start --components=gpg

It seems that the gpg-agent from gnome-keyring-daemon is not compatible with duplicity.

[Netset]

In addition, if you have app-crypt/seahorse-plugins installed, seahorse-agent causes the same issue. To resolve, remove the file /etc/X11/xinit/xinitrc.d/70-seahorse-agent.

[dmp1ce]

As this thread points out, the issue was fixed in gnome-keyring 3.1.91. In Gentoo all I needed to do was install gnome-base/gnome-keyring-3.2.2 and duplicity started to work.