Bug 666326

Summary: evolution - crash in comp_subject
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: jwest, mcrha, rkhadgar, tpelka, vgaikwad
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: evolution-2.32.3-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-27 07:41:54 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:
Bug Depends On: 664329, 666843, 666916, 883010    
Bug Blocks: 782183    
Attachments:
Description Flags
backtrace, disassembly
none
sosreport
none
patch based on upstream code mcrha: review+

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.