gajim trips over new warning output introduced in Gnupg 2.0.23
With the recently released Gnupg 2.0.23, Gnupg will complain on STDOUT if it detects that the Gnome keyring is functioning as a GPG agent. (I’m not really sure about the background, but it could have to do with the Gnome keyring breaking certain smartcard setups.)
The new, unexpected output causes an exception in the thread running common/gnupg.py. Gajim will then presume that the GPG key has not been unlocked, despite the fact that, other than the warning, GnuPG still works fine.
The warning added to Gnupg is as follows:
gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work proberly - please configure that tool to not interfere with the GnuPG system!
Steps to reproduce
Run Gajim 0.15.4 in conjunction with Gnupg 2.0.23.
This is the relevant commit to Gnupg http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=b896fccaada0caf1987eb95ac99dd6b4ca609c4b
Apparently a status code was added so that clients can detect whether the agent communication is relayed via Gnome keyring.
Gajim uses gpg, not gpg2, and it's hardcoded in sources. But even if I change that, I can connect successfully. I don't know how to reproduce that.