GNOME Bugzilla – Bug 618277
Seahorse refuses to sync keys when no servers are selected for personal key publishing CancelOk
Last modified: 2018-08-03 19:19:13 UTC
Created attachment 160725 [details] Seahorse refuses to sync keys, option is greyed out Binary package hint: seahorse lsb_release -rd: Description: Ubuntu 10.04 LTS Release: 10.04 apt-cache policy seahorse seahorse: Installed: 2.30.0-0ubuntu2 Candidate: 2.30.0-0ubuntu2 When selecting “Remote” > “Sync and Publish Keys…” in the Seahorse menu, if no servers are selected for personal key publishing in preferences (“Publish keys to: none, don't publish keys”), Seahorse refuses to sync the “Other keys”. (see screenshot) This means that unless you agree to publish your key(s) to a keyserver, Seahorse will not sync them. Seahorse should not depend on the users will to publish or not to sync keys. Furthermore, if you have ticked the option “Automatically synchronize modified keys with key servers” the keys are never synced and stay out of date. Quick workaround: (from the command line) gpg --refresh-keys --keyserver pgp.mit.edu:11371
-- 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/49.