GNOME Bugzilla – Bug 660445
[abrt] evolution-data-server-3.1.91-2.fc16: __GI_raise: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
Last modified: 2015-03-10 16:50:07 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=742063 abrt version: 2.0.5.980 backtrace_rating: 4 cmdline: /usr/libexec/e-addressbook-factory comment: Trying to auto-complete against LDAP, local address books, and google. crash_function: __GI_raise executable: /usr/libexec/e-addressbook-factory kernel: 3.1.0-0.rc6.git0.3.fc16.x86_64 reason: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT) time: Wed Sep 28 16:32:48 2011 backtrace: warning: core file may not match specified executable file. [New LWP 31413] [New LWP 3923] [New LWP 13773] [New LWP 3926] [New LWP 3924] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/e-addressbook-factory'. Program terminated with signal 6, Aborted.
+ Trace 228638
Thread 4 (Thread 0x7f55b9f4d700 (LWP 3926))
I'm getting this same crash, and can reproduce it at least once a day. Please let me know if you need any additional information from me.
Are your steps similar/same as those above, just autocomplete on the LDAP address book, say in a message composer window?
Yes, exactly the same. I have both an LDAP address book and a google address book and a local address book, just like the original poster. And the crash happens when I was trying to autocomplete an address from the LDAP address book.
Thanks for the update. I looked closely into the place where this crashed, and it's because the e_book_backend_ldap_open() is called when its priv->connected is not FALSE. There is a check in the code for it, the place where it crashes: g_assert (bl->priv->connected == FALSE); It might mean that something is broken with the opening phase of the LDAP addressbook. I tried to reproduce this with anonymous login, and also with the email address login, but both seem to work properly for me, either I cancel the password prompt dialog or provide any or incorrect password (I still authenticate against server which allows anonymous access), but no crash. My server rejects login with DN, thus that one also doesn't crash for me. I'm trying this with 3.2.2 of evolution-data-server and evolution, simply opening new message composer and typing at least three letters to invoke autocompletion of the email address in the "To" field. I can replace the g_assert with something else, but I would like to know what's going wrong here, because th replacement may just hide other issues. Could you run the e-addressbook-factory process from a console, with LDAP debugging on, to see whether it'll show anything useful, please? You can do that with a command like this: $ LDAP_DEBUG=1 /usr/libexec/e-addressbook/factory and when it writes "Server is up and running...", run evolution from another console. Make sure there will be no other e-addressbook-factory process running, because there can be only one in a system. You can also redirect all output from factory to a file, when you append to the command " &>log.txt" (without quotes), though you'll not see the "Server is up and running..." message on the console, because it'll be inside the file.
No duplicate for a long time, I'm closing this.