OS Name Microsoft Windows 7 Ultimate Version 6.1.7600 Build 7600 OS Manufacturer Microsoft Corporation System Type x64-based PC Processor AMD Phenom(tm) 9850 Quad-Core Processor, 2500 Mhz, 4 Core(s), 4 Logical Processor(s) BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 2009-04-22 SMBIOS Version 2.5 Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" Installed Physical Memory (RAM) 4.00 GB Total Physical Memory 4.00 GB Available Physical Memory 1.74 GB Claws Mail version 3.7.4cvs1 System Information GTK+ 2.16.0 / GLib 2.20.0 Locale: en_US (charset: ISO-8859-1) Operating System: Win32 When using _any_ GnuPG functions (signing, encrypting, etc.) the claws-mail client enters a "Not Responding" state in the Windows Task Manager. Forcibly closing the application causes /prompts /allows /unhides the pinentry.exe window requesting the key passphrase. Until claws-mail.exe is force closed, pinentry.exe does not appear in the Task Manager list. Running claws-mail.exe as a standard user, administrative user or with the Windows 7 "Run as Administrator" option does not change this behavior. Nor does any combination or setting in the "Compatibility" option dialog. Entering the passphrase and re-starting claws-mail resolves the problem temporarily, but after a seemingly random period of time (sometimes a few hours, sometimes the next day), the behavior repeats and the client has to be force-closed in order to enter the passphrase. Changing the Passphrase options in Options->Preferences->Plugins->GPG does not appear to make any difference for either selecting or clearing the "Store passphrase ..." or "Grab input ..." option, nor for changing the expire time from 0 to any length up to 500. This also occurs on _different_ GnuPG functions. E.g. if the program is force-closed to sign a message, and then I attempt to sign+encrypt or encrypt a message with the same key, I have to force-close again to enter the passphrase.
This problem can be fixed by putting use-agent in gpg.conf and no-grab in gpg-agent.conf.
I can't reproduce this with 3.12.0. Feel free to reopen if it is still a problem for you.