GPG: “gpg --edit-key name@example.com” yields “Segmentation Fault” [closed]

Question

I can see my key with the same ids for public-and private-keys. When I try to add an uid to the keys with the "--edit-key" command, I get the error:

gpg --edit-key name@example.com

gpg: signal 11 caught ... exiting
Segmentation Fault

[Clarification]

I did the keys with the version "gpg (GnuPG) 1.4.9", while I ran them with "gpg (GnuPG) 1.4.4".

The version of GPG as well as what OS (including version and possible service pack level) you're running would be helpful. To find the version of GPG, run gpg --version and include it's output in your question.
definitely sounds like you should update the old version. you should file a bug too.
I think I was using Ubuntu (or very unlikely Mac). Haven't filled a bug yet but you can see from the time of the question when I found the bug and that way the version. I do not have this kind of problems anymore after switching obsd so I have totally forgotten this issue.
I voted to close this question because it is old. I tested the same thing with Ubuntu's "gpg (GnuPG) 1.4.11" and I cannot get the segmentation fault. It may be that some dev has already fixed this issue. Anyway it does not seem to be current issue unless someone can redo the fault again. Or look version 1.4.9? Q1 2008 version or? Announce day here.

furtelwart · Answer 1 · 2009-11-11 09:16:13Z

The problem could be the version. I just edited a key with GnuPG 1.4.9 and it works perfectly on WinXP SP3.

Try to update to 1.4.9 and edit you key with the new version.

migrated from superuser.com Sep 12 '11 at 22:28