Importing secret key not working

[selzeda]

Binary package hint: seahorse

In Ubuntu 8.10 ("Intrepid"), seahorse 2.24.1 does not import secret keys.

To reproduce the problem, get an ascii armored secret key, for example via the command "gpg --export-secret-key -a <your-name-or-email> --output privkey.asc", and try to import this file into seahorse, either via "seahorse-tool -i privkey.asc" or by starting seahorse, clicking "Keys", "Import..." (or pressing Ctrl+I) and choosing privkey.asc.

Seahorse shows no error message and imports nothing, if you start seahorse from the command line you can see the following error:

** (seahorse:5615): WARNING **: imported key but then couldn't find it in keyring

This seems to a major bug because there seems to be no other way to import an existing private keyfile and thus encrypting files via the nautilus context menu is not possible with an existing key.

Best regards, David

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Jaunty Jackalope.

If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages

[Daniel Holbert (dholbert)]

I just hit this same warning in Ubuntu 10.1...
 ** (seahorse:2658): WARNING **: imported key but then couldn't find it in keyring: [long-key-id]
...but in my case it was because $HOME/.gnupg/pubring.gpg was owned by root for some reason. (I must have accidentally run some command with "sudo" that updated my keyring.)

After running...
  sudo chown $USER.$USER pubring.gpg
...the issue was fixed for me.

(sorry for spamming this bug - I'm only posting here because this* was one of the few pages that came up when I searched Google for the warning)
*or rather a mail-archive.com archive with bugmail from this bug.

[Daniel Holbert (dholbert)]

>I just hit this same warning in Ubuntu 10.1...
Sorry, that should read "Ubuntu 10.10"