|Summary:||Kleopatra crashes the whole system when trying to sign/encrypt the file.|
|Component:||general||Assignee:||Andre Heinecke <aheinecke>|
|Latest Commit:||Version Fixed In:|
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 Thanks.
Comment 2 Justin Zobel 2022-11-04 03:10:29 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-19 05:14:10 UTC
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-04 05:15:40 UTC
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!