Bug 265363

Summary: PIN Entry Window Fails to pop with MS Outlook send operation
Product: [Applications] kleopatra Reporter: jproney
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: major CC: aheinecke, emanuel, mutz
Priority: NOR    
Version: 0.40 (KDE 3.x)   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:

Description jproney 2011-02-04 05:03:21 UTC
Version:           0.40 (KDE 3.x)
OS:                MS Windows

When sending the first message from MS Outlook after opening the applcation, the PIN Entry dialog window fails to appear at all - even in background; causing Outlook to hang and requiring a forced shutdown of Outlook in order to bring the PIN Entry dialog window out. This also causes the message being sent to be lost with no recovery option.  If the PIN Entry cache is cleared anytime between restarting Outlook and sending the first message and sending a subsequent message, again Outlook hangs and the forced-shutdown, PIN Entry and Outlook restart process is again necessary. 

Reproducible: Always

Steps to Reproduce:
To manually reproduce this problem, close Outlook and Kleopatra; the last step causes the PIN cache to clear; then reopen Kleopatra and the Outlook application in that order.  Draft a new e-mail and attempt to send.  

Actual Results:  
On the last send in Steps to Reproduce, Kleopatra should pop the PIN Entry dialog box to the foreground - but doesn't even open it in the background.  Outlook hangs and you have to kill the Send along with OUTLOOK to get the PIN Entry box open.

Expected Results:  
IF pincache = "", then open, in foreground, the PIN Entry dialog box.

OS: Microsoft Windows (i686) release 5.1 (XP Professional)
Compiler: i586-mingw32msvc-gcc
Comment 1 Andre Heinecke 2013-05-08 08:50:42 UTC
The foreground window behavior of pinentry has been improved since. Can you please confirm that this still happens with gpg4win 2.1.0.
Comment 2 Emanuel Schütze 2013-05-10 07:16:51 UTC
I can confirm that this is already fixed in Gpg4win. Please reopen if it is not working for your.