GNOME Bugzilla – Bug 336191
the default keyservers have the wrong protocols which makes the program crashing
Last modified: 2006-04-13 00:44:15 UTC
Steps to reproduce: 1. start seahorse 2. choose a key 3. select Remote->Sync and publish keys 4. select a keyserver from the list 5. start syncing the program crashes I noticed that the keyserver entries were in the form of hkp://server:11371 or ldap://server:11371 I added another keyserver in the http mask which also showed as hpk:// Using the custom form showed a http://pgpkeys/pca.dfn.de:11371. Using this entry I could publish my key. I looks to me that the ldap or hkp part of the serveraddress is responsible for the failure. Stack trace: Other information: seahorse has been updated within the last two days from debian/unstable. I am behind a firewall and router which is distributed by the Deutsche Telecomm (Eumex IP) which is in its original form. No additional ports have been opened so far. I do not know whether it is possible to restrict outgoing traffic. I can modify incoming traffic, but not outgoing.
Can you check which dependencies your seahorse package has? In particular I'm interested it see if something with 'openldap' is listed.
Hi, I can see only libldap2 : Version: 0.9.0-2 Depends: libart-2.0-2 (>= 2.3.16), libatk1.0-0 (>= 1.9.0), libavahi-client3 (>= 0.6.0), libavahi-common3 (>= 0.6.9), libavahi-glib1 (>= 0.6.0), libbonobo2-0 (>= 2.13.0), libbonoboui2-0 (>= 2.5.4), libc6 (>= 2.3.5-1), libcairo2 (>= 1.0.2-2), libdbus-1-2 (>= 0.61), libdbus-glib-1-2 (>= 0.61), libeel2-2 (>= 2.12.0), libfontconfig1 (>= 2.3.0), libgail-common (>= 1.6.6), libgail17 (>= 1.6.6), libgconf2-4 (>= 2.13.5), libglade2-0 (>= 1:2.5.1), libglib2.0-0 (>= 2.10.0), libgnome-keyring0 (>= 0.4.3), libgnome2-0 (>= 2.8.0), libgnomecanvas2-0 (>= 2.11.1), libgnomeprint2.2-0 (>= 2.12.1), libgnomeprintui2.2-0 (>= 2.12.1), libgnomeui-0 (>= 2.8.0), libgnomevfs2-0 (>= 2.13.92), libgnutls12 (>= 1.2.5), libgpg-error0 (>= 1.2), libgpgme11 (>= 1.0.1), libgtk2.0-0 (>= 2.8.0), libgtksourceview1.0-0 (>= 1.4), libice6, libldap2 (>= 2.1.17-1), libnautilus-extension1 (>= 2.9.1), libnotify1, liborbit2 (>= 1:2.10.0), libpanel-applet2-0 (>= 2.12.3), libpango1.0-0 (>= 1.12.0), libpopt0 (>= 1.7), libsm6, libsoup2.2-8 (>= 2.2.91), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxi6, libxinerama1, libxml2 (>= 2.6.23), libxrandr2, libxrender1 (>= 1:0.9.0.2), zlib1g (>= 1:1.2.1), gconf2 (>= 2.10.1-2), debconf (>= 0.5) | debconf-2.0 Bernhard
Could you run seahorse from the terminal and post the failed output here. Also, if the program does indeed crash, could you post a stack trace? Thanks.
Please be so kind to provide some information about stack-tracing. I am willing to do it, but have not done it so far. I have to postpone any further activity till thursday since i am away. Bernhard
Usually when a program crashes, it'll put up a prompt. One of the options in the prompt is 'Inform Developers' When you choose that option, in the following dialogs you can choose to see a stack trace.
I have changed all the entry in the keyserver list to http:<keyserver>:11371 Changing back one entry to hkp:<keyserver>:11371 makes seahorse crash I did not write "hkp" myself, but used the GUI-masked after clicking adding a keyserver. I think if this mask would produce a http instead of hkp everything would be fine. At least with seahorse keyserver settings. Unfortunately, bugzilla does not work properly today. Once that has been settled, I will retry to get a trace. Bernhard
Thanks. I found the crasher in HKP parsing code. I've committed a fix.