Red Hat Bugzilla – Bug 974234
[abrt] Crash in try_open_e_book_cb()
Last modified: 2014-01-02 04:07:30 EST
Description of problem:
evo crashed shortly after resume from s3 sleep.
Version-Release number of selected component:
libreport version: 2.0.9
cmdline: evolution -c mail
:Thread no. 1 (8 frames)
: #0 g_error_free at gerror.c
: #1 g_clear_error at gerror.c
: #2 try_open_e_book_cb at em-utils.c
: #3 open_reply at e-book.c
: #4 reply_cb at gdbusproxy.c
: #5 g_dbus_connection_call_done at gdbusconnection.c
: #6 complete_in_idle_cb at gsimpleasyncresult.c
: #11 IA__gtk_main at gtkmain.c
abrt failed to attach the bt so I'll attach it manually.
Created attachment 760890 [details]
full bt by abrt
Quite similar upstream bug report comment, though without any patch:
The other patches attached on that bug are already part of 2.32.3.
Created attachment 761386 [details]
This makes it work. My reproducer was slightly complicated, because I cheated an LDAP backend, by waiting in its e_book_backend_ldap_load_source() for 5 secodns, which was enough time to switch to other email in evolution's UI.
- have configured one LDAP book, which is set for autocompletion
- have in Edit->Preferences->Mail Preferences->Headers:
[x] Show the photograph of sender in the message preview
[ ] Search for sender photograph only in local addressbooks
- have patch from bug #974647
- have enabled message preview
a) make sure no e-addressbook-factory is running
b) run the factory under gdb like this (answer 'y' on the question):
$ gdb /usr/libexec/e-addressbook-factory \
--ex "b e_book_backend_ldap_load_source" --ex "r -w"
c) once it writes "Server is up and running" switch to another console
and run evolution in mailer:
$ evolution -c mail
d) select a message to view, see a gdb prompt on the factory console
e) select different message, from someone else (that causes cancel of
the pending request)
f) let gdb continue:
g) see evolution crashing down in couple seconds
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.