Bug 592852

Summary: [abrt] crash in evolution-2.28.3-3.el6: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: Lubos Kocman <lkocman>
Component: gtk2Assignee: Benjamin Otte <otte>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: mcrha, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:4158944342d0ebde1f13de7340523f84d061a98d
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:54:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Lubos Kocman 2010-05-17 07:51:52 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Evolution is configured for imap/smtp in redhat
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 4158944342d0ebde1f13de7340523f84d061a98d
kernel: 2.6.32-25.el6.i686
package: evolution-2.28.3-3.el6
rating: 4
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

Comment 1 Lubos Kocman 2010-05-17 07:51:54 UTC
Created attachment 414471 [details]
File: backtrace

Comment 3 Milan Crha 2010-05-17 10:23:36 UTC
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 [1], which was unfortunately closed as invalid. Anyway, looking around for XAllocID bugs I found at least these [2] 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.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=601986

[2] https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&short_desc=XAlloc&bug_status=NEW&bug_status=ASSIGNED&bug_status=CLOSED&short_desc_type=allwordssubstr&product=Fedora&classification=Fedora

Comment 4 Lubos Kocman 2010-05-17 11:02:46 UTC
Hello, yes I use only imap.

Comment 5 RHEL Program Management 2010-06-07 16:03:50 UTC
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
inclusion.

Comment 6 RHEL Program Management 2010-07-15 14:29:14 UTC
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. **

Comment 11 RHEL Program Management 2011-07-06 00:28:42 UTC
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
representative.

Comment 14 RHEL Program Management 2013-10-14 05:24:16 UTC
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.

Comment 15 Jan Kurik 2017-12-06 10:54:15 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/