Page MenuHome GnuPG

Kleopatra: Crash After Verifying Detached Signature
Closed, ResolvedPublic


Expected behaviour

Kleopatra verifies a detached signature without issue.

Actual behaviour

Kleopatra crashes after verifying a detached signature.

Steps to reproduce the behaviour

  1. Launch Kleopatra
  2. Click Decrypt/Verify
  3. Select a detached signature to verify.
  4. A new window appears and the file is verified.
  5. Click OK to close the window.
  6. Kleopatra crashes.

Additional information

GpgEX version 1.0.5 (64 bit)

I tried to re-install Gpg4Win but that did not resolve the issue. I have only tried verifying detached signatures. I asked another person to reproduce the issue but they could not do so. Verification works without issue via command line.

Error windows:

[Window Title]

[Main Instruction]
kleopatra.exe has stopped working

Hang on while Windows reports the problem to Microsoft...

[Window Title]

[Main Instruction]
kleopatra.exe has stopped working

A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]

Note: The following window only appears if verification was performed via the context menu (right-click → More GpgEX options → Verify)

Error returned by the GnuPG user interface:

End of file


Version 3.0.2-gpg4win-3.0.3

Event Timeline

Confirming this bug in Gpg4win version 3.0.3 (previous version was OK).

kleopatra.exe crashes every time after closing verification result window.

Microsoft Windows 10 Enterprise (x64) Build 16299 (1709/RS3), fully patched (with latest Spectre patches as well).

aheinecke triaged this task as High priority.
aheinecke edited projects, added gpg4win; removed gpgex.
aheinecke added a subscriber: aheinecke.

Thanks for your report. I tried this several times. Could not reproduce it at first but I could get it to crash sometimes. Even without GpgEX just by double clicking the signature file.

I'll look into it.

aheinecke changed the task status from Open to Testing.Jan 30 2018, 8:16 AM

Ah under Linux we ran into an assert which made finding the problem easy. The bug was introduced by the fix for T3602. Will be fixed in the next release. Apologies for the inconvenience.

Got confirmation In that this is fixed as my tests also showed this -> resolved.