Red Hat Bugzilla – Bug 592852
[abrt] crash in evolution-2.28.3-3.el6: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Last modified: 2017-01-09 10:54:03 EST
abrt 1.1.1 detected a crash.
Attached file: backtrace
comment: Evolution is configured for imap/smtp in redhat
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
How to reproduce
1. Log off from gnome with evolution running
2. Log in to gnome (evolution is in start up applications on login)
3. Evolution crashed
Created attachment 414471 [details]
Thanks for a bug report. This is same as bug #544759 for Fedora, which was marked as a duplicate and that one moved to an upstream bug , which was unfortunately closed as invalid. Anyway, looking around for XAllocID bugs I found at least these  where subject contains "XAllocID". From that I would assume it's something with gtk2, as stated in bug #559199 comment #3.
I saw something similar upstream too, which was caused by evolution-mapi, calling g_free on something allocated with g_slice or g_slice_free called on a g_new0 memory, I do not recall precisely, but you are mentioning above you are using only IMAP, thus that shouldn't be the case.
Thus I'm moving this to gtk2.
Hello, yes I use only imap.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.