Hide Forgot
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: claws-mail comment: The actual connection to the LDAP server is a port-forwarded connection using ssh. No errors were seen in the terminal window running the ssh connection. component: claws-mail crash_function: ldap_unbind_ext executable: /usr/bin/claws-mail kernel: 2.6.34.7-66.fc13.i686.PAE package: claws-mail-3.7.8-6.fc13 rating: 4 reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1300292602 uid: 1003 How to reproduce ----- 1. Compose a new message 2. Type in the address to look up in the To: line 3. Hit tab to look up the address in the directory 4. Click on the Address icon to open up address dialog 5. Left-click on the LDAP address book icon to look at the settings claws-mail crashes at that point.
Created attachment 485794 [details] File: backtrace
> claws-mail crashes at that point. Always? Could you attach the output of "claws-mail --debug" when reproducing the crash? Somehow it passes on an invalid LDAP connection handle to the openldap library (ldap_unbind_ext) which triggers an assertion. | static gint ldapqry_disconnect( LdapQuery *qry ) { | /* Disconnect */ | if( qry->ldap ) ldap_unbind_ext( qry->ldap, NULL, NULL ); | qry->ldap = NULL; | ... | #0 ldap_unbind_ext (ld=0x29, sctrls=0x0, cctrls=0x0) | at ../../../libraries/libldap/unbind.c:46 | 46 assert( LDAP_VALID( ld ) );
Sorry, I discovered the problem. I did *not* have the LDAP server set to use the correct port-forwarded port in the SSH session. That is, it was trying to open a port that didn't exist. I'm going to close it as NOTABUG.