GPA - unsupported certificate

Peter Lebbing peter at
Mon Dec 7 11:41:16 CET 2015

On 07/12/15 01:24, david at wrote:
> Every Linux distro has gnupg installed - so at a terminal just type gpg -
> this will create ALL the folders and files needed (.gnupg) it's pointless
> installing GPA without running gpg first - I think it's pretty silly.

Eh? I don't find it silly at all. Why would someone, unprompted, fire up a
terminal to initialise the GUI program they installed because they'd rather
use a GUI program than a terminal program? That's like saying you should fire
up Vim before you can use XFCE's Mousepad editor. Well, not really, but it's
still silly to suggest that it is silly to expect a GUI program to do what it
is supposed to do: pretty much replace the command line alternative. Wow, long
complicated sentence. Better end with sentence fragments to compensate.

Anyway, a quick glance at the open bugs for GPA in Jessie[1] show that it is a
problem for people, but developers have difficulty reproducing it. In fact,
those bugs are still open in Sid.

That is, apart from the well-known issue: GNOME Keyring hijacks the agent
connection, which causes all sorts of problems. Up until recently, they were
unwilling to stop breaking GnuPG this way; but recently, they've finally
agreed to provide their functionality in a different way that actually agrees
with the GnuPG architecture.

GPA will get very confused when GNOME Keyring hijacks the agent connection.
For me, Debian Jessie x86_64 with XFCE, I'm pretty sure I fixed it with
"Settings -> Session and Startup", "Application Autostart", uncheck the box
next to "GPG Password Agent (GNOME Keyring: GPG Agent)". But a search on the
web for disabling GNOME Keyring's GPG Agent should provide more information.




I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <>

More information about the Gnupg-users mailing list