GNOME Bugzilla – Bug 758355
generating key with gpg does not produce a key visible under personals key in seahorse
Last modified: 2018-08-03 19:49:47 UTC
Description of problem: Key generated with gpg on the command line does not result in a personal key in Seahorse or one that can be selected in Evolution. Version-Release number of selected component (if applicable): gpg (GnuPG) 1.4.19 How reproducible: gpg --gen-key Steps to Reproduce: 1. Open terminal 2. gpg --gen-key 3. check seahorse for personal gpg key Actual results: No key shows up under personal, just trusted and all. Key can not be selected in Evolution for signing email Expected results: Key shows up under personal in Seahorse and is usable in Evolution Additional info: Using gpg2 command results in personal key. Importing export of key created with gpg also results in personal key.
I seem to be having the same/similar problem. I can't get any public or private gpg keys showing up in seahorse. If I import a key (both public and private) from the cli, it won't show up in seahorse. If I drag an drop a key file into seahorse, It doesn't show up in seahorse. If I generate a new key in seahorse, that new key will show up in seahorse. It seems to be a problem with importing existing keys into seahorse. Ssh keys import just fine in seahorse.
I'm having the same problem, except that I'm not generating my keys by hand, I'm generating them from Seahorse's GUI! And it doesn't even want to display them. This is with Seahorse/GNOME 3.20.x. And yet my old private keys from 2012 still show up in the GUI. What's going on there? Some GPG version incompatibility?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/143.