I'm now seeing this again with 1.0.1. It is definitely not caused by seahorse blocking while it tells gpg to go off and download stuff from the network--seahorse has no child processes of any kind. However gdb reveals some more info:
#0 0xb720d6c7 in ?? () from /usr/lib/debug/libc.so.6 #1 0xb7bf66c7 in ldap_connect_to_host () from /usr/lib/libldap_r.so.2 #2 0xb7be1ff8 in ldap_int_open_connection () from /usr/lib/libldap_r.so.2 #3 0xb7bf4503 in ldap_new_connection () from /usr/lib/libldap_r.so.2 #4 0xb7be1ef1 in ldap_open_defconn () from /usr/lib/libldap_r.so.2 #5 0xb7bf4c78 in ldap_send_initial_request () from /usr/lib/libldap_r.so.2 #6 0xb7bea929 in ldap_sasl_bind () from /usr/lib/libldap_r.so.2 #7 0xb7beadc4 in ldap_simple_bind () from /usr/lib/libldap_r.so.2 #8 0x0809b21d in ?? () #9 0x083c8798 in ?? () #10 0x00000000 in ?? () So it's trying to talk to an ldap server! This should certainly be done in a non-blocking fashion. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
