Seahorse refuses to sync keys when no servers are selected for personal key publishing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse |
Expired
|
Medium
|
|||
seahorse (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
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
Changed in seahorse: | |
importance: | Unknown → Medium |
status: | Unknown → New |
tags: | removed: sync |
Changed in seahorse: | |
status: | New → Expired |
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME)