Initial installation of Kleopatra 3.0.2 on Win 10 HP Pavillion laptop. Tried to generate new key pair. After entering parameters and completing passphrase. The error is generated no matter the length nor content of Passphrase. The message says this could take time to complete but very soon after passphrase is entered the error occurs. Box presented says general error and not much more. Tried different data combinations for the key generation but nothing changed, the error or the quickness of error notification.
First-time installation of Kleopatra on HP Pavillion laptop. Entered info into fields and completed passphrase field. Next box told me it could take some time to generate a key pair. But an error box appeared very quickly afterward that a general error occurred creating the key pair. I tried Changin info, even different passphrases were tried but to no avail.
Hi, thanks for your report but I can't reproduce this (generating a key is of course part of our usual tests). So there must be something in your setup that is unexpected. Could you please try to shutdown kleopatra, move away the directory: %APPDATA%\gnupg then launch Kleopatra and try again. Maybe you have some corrupted files in that directory, that could cause such a failure. If this does not work please start the command line (Hit the Windows + R button and enter cmd) and there run: gpg --gen-key And follow the instructions there. That might produce a better error. Internally this is what Kleopatra would do in the end. Best regards, Andre
Created attachment 109505 [details] attachment-11834-0.html Dear Andre Heinecke; Due to health problems I was delayed replying to your message.I have not been able to get back to our original Kleopatra problem and resolution tried running Kleopatra on Laptop which has been borrowed by family member until After New Years. The kleopatra was started via icon screen showed at bottom of Windows screen. Bringing up a dialog which asks if you want to generate a key pair. Since I never had a key-pair before, I needed a keypair generated. clicked on generate keypair and then ran into problems. Message after first first up of Kleopatra Welcome to Kleopatra 3.0.1-gpg4win-3.0.2 Can this bug be put into deferred status awaiting more info? John ________________________________ From: Andre Heinecke <bugzilla_noreply@kde.org><mailto:bugzilla_noreply@kde.org> Sent: Monday, December 18, 2017 2:05 AM To: montyw47@hotmail.com<mailto:montyw47@hotmail.com> Subject: [kleopatra] [Bug 387978] First time use Key generation Error https://bugs.kde.org/show_bug.cgi?id=387978 Andre Heinecke <aheinecke@intevation.de><mailto:aheinecke@intevation.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Andre Heinecke <aheinecke@intevation.de><mailto:aheinecke@intevation.de> --- Hi, thanks for your report but I can't reproduce this (generating a key is of course part of our usual tests). So there must be something in your setup that is unexpected. Could you please try to shutdown kleopatra, move away the directory: %APPDATA%\gnupg then launch Kleopatra and try again. Maybe you have some corrupted files in that directory, that could cause such a failure. If this does not work please start the command line (Hit the Windows + R button and enter cmd) and there run: gpg --gen-key And follow the instructions there. That might produce a better error. Internally this is what Kleopatra would do in the end. Best regards, Andre -- You are receiving this mail because: You reported the bug.
*** Bug 387904 has been marked as a duplicate of this bug. ***
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 set the bug status 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!
Dear Bug Submitter, 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!