Created attachment 81430 [details]
screenshot showing the error
+++ This bug was initially created as a clone of Bug #322561 +++
Steps to Reproduce:
1.Download Kleopatra 2.1.1 from the software repositories.
Every time I start Kleopatra, it will show the results of its self-tests. One of the tests is called 'Gpg-agent connectivity'. The result of the test is always 'unexpected error'. The explanation message is 'Unexpected error when asking gpg-agent for its version. The error returned was: IPC parameter error.'
I expect to see no error messages when I start Kleopatra.
$ env |grep GPG
I am seeing the same error with Kleopatra 2.0.12 Debian sid (Siduction)
(kernels 3.10.4 or 3.9.4)
env | grep GPG gives nothing
I'm also seeing this on Debian sid gnupg-agent 2.0.22-3
this issue is caused by gnome-keyring hjacking the gpg-agent socket
there are several bugs about this: e.g.
But this issue has developed in an argument between gnome-keyring and gnupg maintainers so while this is basically an Upstream bug Kleopatra should print a Warning about that hjacking instead of an unknown error.
I'm taking this to add a warning similar to the one added in gnupg 2.0.23
The GNOME keyring manager hijacked the GnuPG agent.
GnuPG will not work proberly - please configure that
tool to not interfere with the GnuPG system!
( http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=ffa39be5ebfc1059a737905ee317c9b6f3d2a77e; hp=e184a11f94e2d41cd9266484542631bec23628b5 )
Did not come around to this. In the meantime gnome-keyring and gnupg have resolved the problem. Gnupg provides a pinentry-gnome that integrates with gnome-keyring and gnome-keyring no longer fakes to be a gpg-agent. So i'm marking this as resolved upstream.
Also with gnupg 2.1 this problem never existed as the hijacking did not work with that.
I believe the issue is still on-going: