Kleopatra cannot create a OpenGPG pair key on a fresh installation. When opening the dialog for new certificate, the process goes to the end and stops with a message "Could not create certificate: General error". This is reproduced no matter what options in terms of name, email, desired length of key, or intended use. Reproducible: Always Steps to Reproduce: 1. Open Kleopatra. 2. Open dialog for new certificate. 3. Follow on-screen instructions. 4. Wait for the key to be generated (or write text into the box). Actual Results: The message "Could not create certificate: General error" Expected Results: Generated OpenGPG key. Kleopatra is installed on a 12.04.1 Kubuntu with KDE 4.9.2.
Created attachment 74430 [details] Snapshot from the dialog with the error This snapshot is the last dialog box where the message is displayed and no certificate can be created.
Comment on attachment 74430 [details] Snapshot from the dialog with the error Under the Settings menu you will find an option to Perform Self-test Run the self-test. More than likely you missing a bunch of required packages that you need to install from your distribution. For example you might need gnupg2-smime and dirmngr
I did the test an it passed. I'll attached the snapshot too. I checked your suggestion for missing packages -- both gnupg2-smime and dirmngr are installed.
Created attachment 74433 [details] Snapshot from the self test of Kleopatra The attachment represents the result from the self-test perform in Kleopatra. It seems that all test went through.
Hi, please check if GPG_AGENT_INFO is set to something other then a file that is named like S.gpg-agent If it is not please run gpg from the command line. If you get errors about configuration variables remove them from your gpg.conf. Then try again to generate a key. If it still does not work please use kdebugdialog to activate the debug area of kleopatra and attach the debug output created while you are trying to create a key. Thanks
Hi, Below is the output from Konsole launcged Kleopatra. I see some errors in the first lines, but they do not ring a bell to me. -------START---- QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied QFileSystemWatcher: failed to add paths: /home/gkourtev/.gnupg/pubring.gpg chan_19 -> OK GPG UI server (Kleopatra/2.1.1) ready to serve gkourtev@gkourtev-laptop:~$ chan_18 <- OK GPG UI server (Kleopatra/2.1.1) ready to serve chan_18 -> GETINFO pid chan_19 <- GETINFO pid chan_19 -> D 11426 chan_19 -> OK chan_18 <- D 11426 chan_18 <- OK Server PID = 11426 chan_18 -> BYE chan_19 <- BYE chan_19 -> OK closing connection ChecksumDefinition[ "sha1sum" ] ("xargs", "-0", "sha1sum", "--") ChecksumDefinition[ "sha1sum" ] find -print0 | "/usr/bin/xargs" ("-0", "sha1sum", "--") ChecksumDefinition[ "sha1sum" ] ("sha1sum", "-c", "--") ChecksumDefinition[ "sha1sum" ] "/usr/bin/sha1sum" ("-c", "--") "%f" () ChecksumDefinition[ "md5sum" ] ("xargs", "-0", "md5sum", "--") ChecksumDefinition[ "md5sum" ] find -print0 | "/usr/bin/xargs" ("-0", "md5sum", "--") ChecksumDefinition[ "md5sum" ] ("md5sum", "-c", "--") ChecksumDefinition[ "md5sum" ] "/usr/bin/md5sum" ("-c", "--") "%f" () QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied QFileSystemWatcher: failed to add paths: /home/gkourtev/.gnupg/pubring.gpg kleopatra(11426)/kdeui (kdelibs): Attempt to use QAction "key_search_bar" with KXMLGUIFactory! -----END-----
I'm also getting this issue.
Andre, does comment #6 provide the requested information? Please set the bug status.
No response, changing status.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!
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!
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!