After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618277 - Seahorse refuses to sync keys when no servers are selected for personal key publishing CancelOk
Seahorse refuses to sync keys when no servers are selected for personal key p...
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2010-05-10 14:50 UTC by axx
Modified: 2018-08-03 19:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Seahorse refuses to sync keys, option is greyed out (12.44 KB, image/png)
2010-05-10 14:50 UTC, axx 		Details

Description axx 2010-05-10 14:50: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
Comment 1 GNOME Infrastructure Team 2018-08-03 19:19:13 UTC 
-- 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.