kleopatra-3.5.6-0ubuntu6 fails to generate SSL keypair using gpgsm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdepim (Ubuntu) |
Invalid
|
Undecided
|
Rich Johnson |
Bug Description
Binary package hint: kleopatra
When I click on "Generate Key Pair & Certificate Request", the GnuPG log shows:
[2007-07-
[client at fd 4 connected]
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> # Home: ~/.gnupg
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> # Config: /home/mark/
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> # AgentInfo: /tmp/seahorse-
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> # DirmngrInfo: [not set]
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> OK GNU Privacy Guard's S/M server 2.0.3 ready
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: <- OPTION display=:0.0
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> OK
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: <- OPTION lc-ctype=
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> OK
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: <- OPTION lc-messages=
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: -> OK
4 - 2007-07-18 22:34:42 gpgsm[13454.0] DBG: <- INPUT FD=12
4 - 2007-07-18 22:34:43 gpgsm[13454.0] DBG: -> OK
4 - 2007-07-18 22:34:43 gpgsm[13454.0] DBG: <- OUTPUT FD=15
4 - 2007-07-18 22:34:43 gpgsm[13454.0] DBG: -> OK
4 - 2007-07-18 22:34:43 gpgsm[13454.0] DBG: <- GENKEY
After a second ot two, the kleopatra "Generating Key" status dialog opens and then nothing happens.
I have looked at lsof output and detected that gpgsm is listening on FD 12, but kleopatra (and also every other process) is not connected to it at all on the other side of that pipe!
At other occasions, I get "bad IPC call" messages, so I guess there is something badly wrong with the pipe handling or there is simply a version mismatch between kleopatra and gpgsm 2.0.3-1ubuntu1.
Are you still experiencing this issue? I am having problems trying to confirm this because KLeopatra won't even run for me. I have never used it so I am a bit inexperienced with it. I can find someone online to see if they can confirm if it is still an issue. Thanks!