Bug 379200 - Kleopatra crashes the whole system when trying to sign/encrypt the file.
Summary: Kleopatra crashes the whole system when trying to sign/encrypt the file.
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.2.0
Platform: Other Microsoft Windows
: NOR normal (vote)
Target Milestone: ---
Assignee: Andre Heinecke
Depends on:
Reported: 2017-04-25 14:57 UTC by raghavendra_rao
Modified: 2017-04-25 18:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description raghavendra_rao 2017-04-25 14:57:29 UTC
We are able to launch Kleopatra, but it crashes the whole system (in this case it's a Windows Virtual Environment)
We have run process explorer to identify at what point it crashes and it was identified that as soon the Kleopatra tries to execute PinEntry.exe the whole virtual session freezes.

With this we are unable to run any debugging or procmon tools to see what is happening.

Could I request you to look into this please?
Comment 1 Andre Heinecke 2017-04-25 18:05:02 UTC
There has to be something special in your environment because it usually does not do this. We are mainly testing in VirtualBox windows VM's. Maybe some security Software? Do you have some "Anti Virus" solution installed they are often the cause of strange problems?

What is your Virtualisation software?

The default pinentry (pinentry-qt) uses some aggressive hacks to become the foreground window. E.g. it tries to attach itself to the current foreground thread to raise itself. That may be an issue. We ship alternative pinentries.

In the Gpg4win installation directory please rename "pinentry.exe" to something else and rename pinentry-w32.exe to pinentry.exe

Pinentry-w32 is ugly but may be more robust. You can also try pinentry-gtk as a compromise between uglyness and robustness but I think this requires that you have installed GPA.

It would also be helpful if you could confirm that this is still an issue in the upcoming gpg4win 3.0 https://wiki.gnupg.org/Gpg4win/Testversions