Bug 386518 - Decrypt and verify both crash
Summary: Decrypt and verify both crash
Status: RESOLVED NOT A BUG
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 3.0.0
Platform: Other Microsoft Windows
: NOR critical
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-04 08:01 UTC by gsrd
Modified: 2018-05-17 00:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gsrd 2017-11-04 08:01:45 UTC
I am attempting to decrypt a file.  The decryption process proceeds to 100% and then Kleopatra crashes with the following:

Runtime Error!

Program: C:\Program Files (x86)\Gpg4win\bin\kleopatra.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Comment 1 rbdj 2018-03-06 22:35:47 UTC
Same problem over here. 
Is anybody looking into this?
Comment 2 Andre Heinecke 2018-03-07 14:14:46 UTC
We had a crash in Kleopatra on Verify that has been fixed:
https://dev.gnupg.org/T3761 (Or here BUG 389792 )

We also fixed instabilities of Kleopatra when used with a APPDATA directory that lives on a UNC path (\\Server\foo\). Maybe this is the case for you, too?

For decryption I was unable to reproduce a crash.

Could you try with the latest beta https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe if this crash still exists for you?

And if so could you add more details what exactly are your steps to make it crash?
Comment 3 Christoph Feck 2018-03-29 23:50:22 UTC
If you can provide the information requested in comment #2, please add it.
Comment 4 Christoph Feck 2018-04-26 21:37:41 UTC
To further investigate this issue, KDE developers need the information requested in comment #2. If you can provide it, or need help with finding that information, please add a comment.
Comment 5 Christoph Feck 2018-05-17 00:33:31 UTC
No response; changing status. If you have new information, please add a comment.