Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
evo crashed after I hit "Reply all" to an email message
Version-Release number of selected component:
evolution-2.28.3-30.el6
Additional info:
libreport version: 2.0.9
abrt_version: 2.0.8
backtrace_rating: 4
cmdline: evolution -c mail
crash_function: g_slice_free1
kernel: 2.6.32-358.el6.x86_64
truncated backtrace:
:Thread no. 1 (10 frames)
: #2 g_slice_free1 at gslice.c
: #3 g_slist_remove at gslist.c
: #4 ltable_next_cnxn at gconf-listeners.c
: #5 gconf_listeners_add at gconf-listeners.c
: #6 e_source_list_new_for_gconf at e-source-list.c
: #7 e_book_get_addressbooks at e-book.c
: #8 e_name_selector_entry_init at e-name-selector-entry.c
: #9 g_type_create_instance at gtype.c
: #10 g_object_constructor at gobject.c
: #12 g_object_new_valist at gobject.c
Thanks for a bug report. This is caused by a thread non-safety of GConf, as indicated here:
https://bugzilla.gnome.org/show_bug.cgi?id=627358
and here, with its duplicates:
https://bugzilla.gnome.org/show_bug.cgi?id=619567
Except of the first bug there was no exact fix in this, beside architecture change in evolution-data-server and evolution, basically where the place to save account information is saved, in time of 3.6.x.
Looking closely to the backtrace, your issue is the first bug. The commit Matthew mentioned is this one [1], but it changes public API, which might mean to rebuild all dependent packages in RHEL to be sure it didn't break anything. I'm not sure how much it is doable. Maybe if we'll not deprecate the old function and will use the new in ENameSelector, then it'll be fine.
[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=7494d975b37e250f78964b11a768dfea06c6f780
Created attachment 744779[details]
evolution-data-server-2.28.3-name-selector-load.patch
for evolution-data-server;
Backport of Matthew's patch, without changing existing API.
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.
http://rhn.redhat.com/errata/RHSA-2013-1540.html