seahorse does not synchronize keys with keyserver

Bug #117514 reported by Wolf Rogner on 2007-05-29
96
This bug affects 14 people
Affects Status Importance Assigned to Milestone
seahorse
Expired
High
seahorse (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: seahorse

In preferences / keyserver

1. add a new key server: HTTP key server "keyserver.pgp.com"
2. select as default
3. in main window / My personal keys select key
4. right click -> Sync and Publish keys ...

Dialog: Synchronizing keys: Connecting to keyserver.pgp.com:11371

After some time (5mins) an error dialog shows up: Could not synchronize keys

Keys are not synchronized to the server.

Sometimes seahorse crashes after sync-attempts (did not find a pattern yet)

Wolf Rogner (war-rsb) wrote :

OK: here is the correct error message:

Couldn't publish keys to server: hkp://keyserver.pgp.com

Couldn't communicate with server 'keyserver.pgp.com': Cannot connect to destination

Kyubutsu (jf) wrote :

confirmed on 8.04 hardy x86_64
error message on [sync and publish key] function:
"couldn't publish key to keyserver: ldap://keyserver.pgp.com
   entry has no objectClass attribute"

Wolf Rogner (war-rsb) wrote :

Does this still exist in your environment?

For me it's fixed. I can sync with any key server

For me it has crashed every time I do a sync. First after 2-3 minutes I get an error about problem with communication to pgp.mit.edu 11371. After that it crashes and I see this in my syslog:

May 8 12:37:22 thonov-ubuntu kernel: [ 3069.487809] seahorse[24677]: segfault at 00000010 eip b7454e5d esp bfe5c420 error 4

However, now when I repeated it I successfully synced two times in a row! Since then I removed that keyserver and re-added it (custom, hkp://pgp.mit.edu:11371). Maybe that solved it?!

I can confirm this in hardy x86_64
"couldn't publish key to keyserver: ldap://keyserver.pgp.com
   entry has no objectClass attribute"

However, Im able to publish to hkp://keyserver.ubuntu.com:11371.

Léo Studer (leo-studer) wrote :

I confirm this bug on hardy x86_64

Wolf Rogner (war-rsb) wrote :

Can we close this by now? No updates since 26.6.2008.

Léo Studer (leo-studer) wrote :

The bug is still present so I don't see any reason why we should close it right now. Furthermore 26.6.2008 was less than 10 days ago!

Joel Berger (joel-a-berger) wrote :

I confirm: cannot sync to ldap from x86_64 Hardy

harcesz (harcesz) wrote :

same, hardy (8.04) but got this error since i started using PGP and seahorse (which is great otherwise)

Andreas Moog (ampelbein) wrote :

Now with version 2.23.90-0ubuntu1 i can synchronize to every server i want to. Is it solved for the rest of you, too?

Changed in seahorse:
status: New → Incomplete
Leif Walsh (leif.walsh) wrote :

I still get 'entry has no objectClass attribute' when I try to publish to keyserver.pgp.com, and keyserver.ubuntu.com is currently in the process of timing out again.

Andreas Moog (ampelbein) wrote :

Thanks for the Update. What version of seahorse are you using? Could you try with Intrepid Ibex Live-CD?

Changed in seahorse:
assignee: nobody → andreas-moog
importance: Undecided → Low

On Fri, Sep 5, 2008 at 3:06 PM, Andreas Moog <email address hidden> wrote:
> Thanks for the Update. What version of seahorse are you using? Could you
> try with Intrepid Ibex Live-CD?

Version: 2.23.91-0ubuntu1

I can't try right now, but once I get my laptop I can (this will be a
while, do your best not to block on me). gpa 0.7.6 also has this
problem (says "Invalid Argument" and crashes with no debugging info),
so this may be a deeper problem than I thought, or something totally
separate.

--
Cheers,
Leif

Andreas Moog (ampelbein) wrote :

Seems I picked the wrong keyserver to synchronize in the first place. It's still an issue for me, I've linked the upstream bugreport. You can track the status and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=401655

Changed in seahorse:
assignee: andreas-moog → desktop-bugs
status: Incomplete → Triaged
Changed in seahorse:
status: Unknown → Confirmed
Oleksij Rempel (olerem) wrote :

I have same proble. I think best workaround for Intrepid is to remove ldap://keyserver.pgp.com from the server list-

Oleksij Rempel (olerem) wrote :
Oleksij Rempel (olerem) wrote :

Here is smole corection in last patch

Here is an diff with your Patch included. Can anyone test it?

@ Martin

Seahorse uses quilt for patch management, so you shouldn't patch the source directly. There is already a patch in quilt editing that line, so you'd probably want to edit that patch. It can be found in:

debian/patches/11_ubuntu_keyserver.patch

Ok, thank you Andrew

Derek White (d-man97) wrote :

Official 8.10 Intrepid
seahorse 2.24.1

Backed-up my secring.gpg & pubring.gpg from my old 8.04 system and imported it using Key->Import.

Made some changes to my key, but really didn't change anything.

Sync to ldap://keyserver.pgp.com gives this:
   <big><b>Couldn't publish keys to server</b></big>
   entry has no objectClass attribute

Sync to hkp://pgp.mit.edu:11371 gives this:
   <big><b>Couldn't publish keys to server</b></big>
   Error decoding keyblock

Is this a regression?

Random question/comment while I have your attention: Why does seahorse let me sign my own key, when it really doesn't do anything, and doesn't even tell me that nothing was done?

I can confirm that I have EXACTLY the same as the last commentor - its not working on a fresh install of Ubuntu 8.10

Official 8.10 Intrepid
seahorse 2.24.1

Backed-up my secring.gpg & pubring.gpg from my old 8.04 system and imported it using Key->Import.

Made some changes to my key, but really didn't change anything.

Sync to ldap://keyserver.pgp.com gives this:
   <big><b>Couldn't publish keys to server</b></big>
   entry has no objectClass attribute

Sync to hkp://pgp.mit.edu:11371 gives this:
   <big><b>Couldn't publish keys to server</b></big>
   Error decoding keyblock

It doesn't work for me either (II 64-bit, seahorse 2.24.1).

Key servers:
hkp://pgp.mit.edu:11371
ldap://keyserver.pgp.com

Error message:
<big><b>Couldn't publish keys to server</b></big>
Error decoding keyblock

Regards, Nikos

dud (herve-werner) wrote :

Read from http://ubuntuforums.org/showthread.php?t=289992

I think this could be related to this bug http://bugzilla.gnome.org/show_bug.cgi?id=351966 regarding the use of images in keys not working with older servers like the mit one. I removed the image from my key and it's working for me now.

I tried and it worked for hkp://pgp.mit.edu:11371 but not for ldap://keyserver.pgp.com.

Same here, "entry has no objectClass attribute" in a fresh install of Ubuntu 8.10...

Michael Nagel (nailor) wrote :

i can confirm that on my up-to-date intrepid i get the exact same results as commenter #24

<big><b>Couldn't publish keys to server</b></big>

Error decoding keyblock

harrykar (harrykar) wrote :

Definitely confirm Michael Nagel and others with the same problem. I also obtain

<big><b>Couldn't publish keys to server</b></big>

Error decoding keyblock

with publication of pgp keys. Instead for ssh keys i not see any advise.
Please workaround and take it high TIA :-)

nh2 (nh2) wrote :

Confirmed on a fully updated Intrepid Ibex.

Using the OOTB configuration for seahorse (2.24.1) and Ubuntu 8.10 I get the following error message

<big><b>Couldn't retrieve keys from server: keyserver.pgp.com</b></big>
Transport endpoint is not connected

If I remove the server ldap://keyserver.pgp.com the message dissapear.

If I include a picture on the key I am trying to upload to hkp://pgp.mit.edu:11371 (which documents it does not support that feature) i get the following error message:

<big><b>Couldn't publish keys to server</b></big>
Error decoding keyblock

In summary, remove the ldap keyserver from pgp and do not include pics and it should work.

Chucky Ellison (ellisonch) wrote :

I was receiving "<big><b>Couldn't publish keys to server</b></big> Error decoding keyblock" from MIT until I removed my picture as suggested by Carlos. That worked---thanks!

A. Denton (aquina) wrote :

I can confirm that behavior for Xubuntu 8.04.3 LTS and Seahorse 2.22.2. After removing "ldap://keyserver.pgp.com" and leaving only "hkp://pgpkeys.pca.dfn.de" (German research network) it all worked out fine - even with user images.

David Futcher (bobbo) on 2010-06-11
tags: added: patch-needswork
Changed in seahorse (Ubuntu):
status: Triaged → Opinion
status: Opinion → Confirmed
Changed in seahorse:
importance: Unknown → High
David Ayers (ayers) wrote :

Switching away from buggy servers may be useful workaround for current stable releases, but seahorse should gracefully handle buggy servers and inform the user of the issue.

A. Denton (aquina) wrote :

The bug is still assigned to Ubuntu Desktop Bugs team and gnome-bugs #401655 in status confirmed. Can someone there provide us with an update with regards to the issue/bug?

Changed in seahorse:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.