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.
Bug 666326 - evolution - crash in comp_subject
Summary: evolution - crash in comp_subject
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 664329 666843 666916 883010
Blocks: 782183
TreeView+ depends on / blocked
 
Reported: 2010-12-30 05:54 UTC by Siddharth
Modified: 2018-11-26 19:28 UTC (History)
5 users (show)

Fixed In Version: evolution-2.32.3-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-27 07:41:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
backtrace, disassembly (55.29 KB, text/plain)
2010-12-30 05:56 UTC, Siddharth 		no flags Details
sosreport (359.66 KB, application/x-xz)
2010-12-30 05:56 UTC, Siddharth 		no flags Details
patch based on upstream code (2.66 KB, patch)
2011-01-03 19:12 UTC, ritz 		mcrha: review+
Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 597567 0 None None None Never

Description Siddharth 2010-12-30 05:54:32 UTC 
Description of problem:
abrt version: 1.1.13
Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.32-71.7.1.el6.x86_64
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time: 1291169422
uid: 500 

Version-Release number of selected component (if applicable):
evolution-2.28.3-10.el6
Red Hat Enterprise Linux Workstation release 6.0 (Santiago)

How reproducible:
Random crash

Steps to Reproduce:
1.
  
Actual results:
Evolution killed.

Expected results:
Evolution should not killed.

Additional info:
Comment 1 Siddharth 2010-12-30 05:56:06 UTC 
Created attachment 471144 [details]
backtrace, disassembly
Comment 2 Siddharth 2010-12-30 05:56:46 UTC 
Created attachment 471145 [details]
sosreport
Comment 4 ritz 2011-01-03 19:12:42 UTC 
Created attachment 471540 [details]
patch based on upstream code

prereq - eds and libical to be patched ( check bz blocks )
Comment 6 Milan Crha 2011-01-17 10:22:35 UTC 
Comment on attachment 471540 [details]
patch based on upstream code

I'm not sure of the first chunk, but otherwise it seems like a copy of the upstream patch, so feel free to use it. When the libical update will be done, and evolution rebuilt against it, then the fix will work.
Comment 11 RHEL Program Management 2011-07-06 00:22:55 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 13 RHEL Program Management 2012-12-14 06:51:15 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 Milan Crha 2013-05-09 17:38:27 UTC 
Upstream fix is part of 2.32.3, thus I mark this as a dependency to the rebase bug.
Comment 16 Milan Crha 2013-06-10 12:36:44 UTC 
I would close this bug as obsolete, there is nothing to change on evolution side, except of rebuild against newer libical, if any. Once the rebuild will happen, the change included in 2.32.3 will start working.
Comment 17 Milan Crha 2013-06-27 07:41:54 UTC 
Closing due to comment #15, once the libical will be updated, and the evolution rebuilt against it, then the included fix will start working.
Note You need to log in before you can comment on or make changes to this bug.