Gpg4win doesn't include libexpat anymore (since it doesn't include gpa and pinentry-gtk anymore).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 5 2023
Mar 19 2023
Mar 17 2023
We stopped maintaining GPA in favor of Kleopatra.
Sep 17 2022
Finally had some time to look into this a bit more.
Mar 14 2022
A simple first step would be to install pinentry-gtk only in the GPA variant.
Mar 11 2022
I think this is because we install pinentry-gtk, too. So we have that GTK dependency.
Jan 3 2022
Oct 13 2021
Sep 8 2021
I verified that manually putting the DB in WAL mode also resolved this issue, since writers don't block readers in WAL mode.
Aug 13 2021
May 11 2021
Thanks for using GPA. Unfortunately, I have to tell you that GPA development has been stopped and I can't say whether we will fix that bug any time soon. Please consider to switch to Kleopatra which is the standard key manager included in gpg4win.
Apr 15 2021
Done for gpa.
Please test.
Done for pinentry.
Jan 23 2021
Jan 5 2021
Dec 10 2020
Dec 9 2020
I have reproduced the bug
A backtrace with gdb from migw-w64 results in
I did a fresh install of Gpg4win 3.1.14 and imported my standard pubkey, by using
gpg --locate-key bernhard@intevation.de
on the command line.
Sorry, I can' reproduce thus. What kind of key is causing the crash?