Page MenuHome GnuPG

Recipient dialog causes Outlook SP2 to crash
Closed, ResolvedPublic

Description

GPGOL with Outlook 2003SP2 (all patches) causes crash of Outlook whenever the
recipient dialog window appears. This crash occurs immediately after the window
is closed regardless of the key selected and Windows then offers to send a
report to Microsoft.

Failure is 100% reliable on this system (and others at this location). I'd
attach a copy of the information windows offers to send but I cannot select the
text within the window. Let me know what info is required & I will try to obtain it.

Environment
WinXP Pro 2002 SP2, Outlook 2003 SP2 (all patches downloaded).
GPG4WIN 1.0.6
Connecting to Exchange server

regards

Andy

Event Timeline

GPGol has an extra debug options which helps to understand the internal
communication between Outlook and GPGol. To enable it, go to the GnuPG tab in
Outlook's option page, click on the "Advanced" button and enter

c:\temp\gpgol.log

into the "Debug output" field. You should check that file for sensitive
information before posting it. I you feel uneasy to have them in the tracker,
just post them to Timo (twoaday at freamail dot de) me (wk@gnupg.org).

Have uploaded the logfile actions as below:

  1. Open Outlook with clean logfile
  2. New message (encrypt+sign), send
  3. Recipient dialog come up
  4. Select key
  5. BANG Outlook dies and restarts
  6. Logfile copied and uploaded here...

BTW,
It makes no difference if I sign or not - it appears the recipient dialog is
what kills things.

regards

Andy

Have uploaded the log as described.

thanks for the response.

regards

Andy

-----Original Message-----
From: Werner Koch via BTS [mailto:gnupg@bugs.g10code.com]
Sent: 05 September 2006 12:32
To: Andy Fletcher; twoaday@g10code.com; wk@gnupg.org
Subject: [issue697] Recipient dialog causes Outlook SP2 to crash

Werner Koch <wk@gnupg.org> added the comment:

GPGol has an extra debug options which helps to understand
the internal
communication between Outlook and GPGol. To enable it, go to
the GnuPG tab in
Outlook's option page, click on the "Advanced" button and enter

c:\temp\gpgol.log

into the "Debug output" field. You should check that file
for sensitive
information before posting it. I you feel uneasy to have
them in the tracker,
just post them to Timo (twoaday at freamail dot de) me (wk@gnupg.org).


status: unread -> chatting


g10 Code's BTS <gnupg@bugs.g10code.com>
<T697>


The bug has actually been fixed in a working copy but not propagated to the SVN
at the time I did the 1.0.6 release. We are currently looking whether we need
to do another gpgol and gpg4win release now.

Timo, what about a new release?

I will do a last test with the current SVN code, but I can't see any reason why
we shouldn't make a new release.