Can't synchronize keys using Seahorse

[Robert J. Hansen]

> How can I fix this?

Specify a different keyserver.

keyserver.pgp.com was a commercial keyserver run by PGP Corporation, or 
whichever corporate entity owned the PGP intellectual property at the 
time.  Network Associates gave way to PGP Security gave way to Symantec 
gave way to...

The PGP intellectual property is for all intents and purposes dead at 
this point.  Symantec has even stopped using the PGP trademarks: they 
may still sell the software, but they've stopped issuing new releases 
and they've rebranded it to something as bland as cottage cheese.

keyserver.pgp.com is still operational today, but nobody knows for how 
long.  It would be wise to assume that it will go away at some point, 
and start migrating to another keyserver.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x1E7A94D4E87F91D5_and_old_rev.asc
Type: application/pgp-keys
Size: 60806 bytes
Desc: OpenPGP public key
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20220217/8c0c8e18/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20220217/8c0c8e18/attachment-0001.sig>