Bug 2140 - Windows 7 ultimate
Summary: Windows 7 ultimate
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (Windows)
Classification: Unclassified
Component: default (show other bugs)
Version: 3.7.6
Hardware: PC other
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2010-03-13 01:37 UTC by michael.mehrtens
Modified: 2012-09-12 10:26 UTC (History)
1 user (show)

See Also:


Attachments

Description michael.mehrtens 2010-03-13 01:37:53 UTC
By signing or encrypting a mail with Gnupg the mail service do not answer... After breaking te dead lock manualy ( with task manager) the passphrase input window appears, but the mail is not sended, and is stored in qued folder. what is the solution??? to get an runing well mail service. Have a nice week end and thanks for answer.
Michael
Comment 1 Ed V 2010-03-22 19:18:24 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.
Comment 2 Colin Leroy 2010-12-18 21:05:12 UTC
Does that still happen ?
Comment 3 Ed V 2010-12-19 02:43:20 UTC
Yes, but only with the QT version of the executable.

If I switch back to the GTK+ version, it works as expected.
Comment 4 Colin Leroy 2012-09-12 10:26:33 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.