Summary: | Windows 7 ultimate | ||
---|---|---|---|
Product: | Claws Mail (Windows) | Reporter: | michael.mehrtens |
Component: | default | Assignee: | users |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | incidentr |
Priority: | P3 | ||
Version: | 3.7.6 | ||
Hardware: | PC | ||
OS: | other |
Description
michael.mehrtens
2010-03-13 02:37:53 UTC
I think this is describing the same issue I have. 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. 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. Does that still happen ? Yes, but only with the QT version of the executable. If I switch back to the GTK+ version, it works as expected. This bug should be reported to Gpg4win in my opinion. If the results differ when pinentry.exe differs, I don't think it can be Claws' fault. |