SUMMARY I install gpg4win in Windows and I make a new gpg key. The "Use GPG encrytion" is grey out in the XML Storage plugin. The path of the user home directory in Linux is ~/.gnupg, and it is not working in Windows. Please add an option for Windows, homedir = "%HOMEDRIVE%%HOMEPATH%\.gnupg". The user homedir of gpg4win actually is %HOMEDRIVE%%HOMEPATH%\AppData\Roaming\gnupg". If the Windows options have these two choices, that will be great. Thanks, Andrew
Git commit 96045daafb56188b72e8930ae17ff6c3f60ff245 by Thomas Baumgart. Committed on 30/09/2018 at 13:56. Pushed by tbaumgart into branch '5.0'. Scan for gnupg home dir location Scan for the secret keyring file by traversing the home directory and the application data directories known to QStandardPaths and some know subdirectory combinations. M +51 -0 kmymoney/plugins/xml/libkgpgfile/kgpgfile.cpp https://commits.kde.org/kmymoney/96045daafb56188b72e8930ae17ff6c3f60ff245
I test on Version 5.0.80-90212a2b GPG encryption of XML Storage is not working in Windows even after the patch from Thomas. The libraries of kf5-gpgmepp and gpgmepp are missing. These are what I notice so far, I will dig into it. Thanks, Andrew
Created attachment 133765 [details] GpgME not installed correctly error Hi, Please see attached screenshot of the error I get. I am using Gpg4Win 3.14. Any help much appreciated. Best regards, Nigel
(In reply to Andrew Ho from comment #0) > The user homedir of gpg4win actually is > %HOMEDRIVE%%HOMEPATH%\AppData\Roaming\gnupg". See https://invent.kde.org/office/kmymoney/-/merge_requests/78 for a related merge request.
Git commit 2cc89fc6c77c4f42e11c92f5ca0ddccd5c2a15ae by Thomas Baumgart. Committed on 28/04/2021 at 08:08. Pushed by tbaumgart into branch '5.1'. Change order to search for GPG configuration directory FIXED-IN: 5.1.2 (cherry picked from commit 26b13d33fe7859dcaaf93a1139d3768336c7aa36) M +88 -58 kmymoney/plugins/xml/libkgpgfile/kgpgfile.cpp https://invent.kde.org/office/kmymoney/commit/2cc89fc6c77c4f42e11c92f5ca0ddccd5c2a15ae
*** Bug 435948 has been marked as a duplicate of this bug. ***