Comment 53 for bug 201786

I had this problem today, with Karmic. The problem went away after a logged out and logged back in - I'm not sure what the problem is with older versions, but I think in Karmic the problem is that seahorse does not update with the new key when a new key is created while it is running.

If you try to kill seahorse, you're going to kill your X session because seahorse is running under dbus-launch. Obviously logging out whenever you create a new SSH key is not a good workaround.