Bug #79

gpgme on 64bit windows fails to find gpg

Added by b ounce almost 7 years ago. Updated almost 7 years ago.

Status:NewStart date:07/06/2012
Priority:NormalDue date:
Assignee:-% Done:


Category:WindowsSpent time:-
Target version:-


This is really a bug in gpgme but a quick search did not turn up a bug reporting place for them; kindly forward upstream.

Sylpheed fails to find gpg.exe on 64bit windows 7 apparently because gpgme looks in the wrong place (Under "Program Files" instead of "Program Files (x86)". gpgme also does not provide an override mechanism as according to an old mailing list message such a thing "does not make sense". The end result is that gpg functions are unavailable in sylpheed despite both appear to be correctly installed, in fact are simple stock installations of the gpg4win and sylpheed distributions respectively. Apparently dysfunction makes more sense than function to the upstream. Tested with 3.1.? and verified still a problem with 3.2.


#1 Updated by Takumi Nakamura almost 7 years ago

GPG4WIN includes gpg2.exe not gpg.exe.
Let's copy "Program Files (x86)\GNU\GnuPG\gpg2.exe" to "gpg.exe", not shortcut.
It work Sylpheed 3.2.0 and GPG4WIN 2.1.0.

GPGME read "Install Directory" on HKEY_LOCAL_MACHINE/Software/GNU/GnuPG.
ReqOpenKeyExA will redirect to HKEY_LOCAL_MACHINE/Software/Wow6432Node/GNU/GnuPG
on 64bit environment.


value of "Install Directory" is "C:\Program Files (x86)\GNU\GnuPG".

#2 Updated by Takumi Nakamura almost 7 years ago

I suggest this problem to GnuPG BTS.


As a result, GPGME official version (on Windows) is in GPG4WIN currently.
this version search gpg2.exe not gpg.exe.
It is patched by gpg4win-*/patches/gpgme/01-gpg2.patch.

When we build Sylpheed binary for GPG4WIN, it is necessary to use GPGME in GPG4WIN.

Also available in: Atom PDF