Bug 449918

Summary:	'Segmentation fault' pops up while creating VFolder
Product:	Red Hat Enterprise Linux 3	Reporter:	Hao Liu <hliu>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED WONTFIX	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9	CC:	desktop-bugs, hliu, llim
Target Milestone:	---	Keywords:	Desktop
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 16:07:42 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:

Description Hao Liu 2008-06-04 09:32:35 UTC

Description of problem:
When users try to create a new VFolder for an existing mail, error dialog box
complaining 'Segmentation fault' pops up.

Version-Release number of selected component (if applicable):
evolution-1.4.5-21.el3.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Select an existing mail.
2. 'Tools' -> 'Create Virtual Folder From Message' -> 'VFolder on Subject' or
'VFolder on Sender' or 'VFolder on Recipients' or 'VFolder on Mailing List'
  
Actual results:
Dialog box pops up complaining 'Segmentation fault'

Expected results:
Selected mail appears in the newly created VFolder


Additional info:

1. rpm -qa | grep evolution
evolution-devel-1.4.5-21.el3.x86_64
evolution-connector-1.4.7-10.x86_64
evolution-1.4.5-21.el3.x86_64
evolution-debuginfo-1.4.5-21.el3.x86_64

If there's other info you need to know, please drop me a mail, thanks a lot.

Comment 1 Jiri Pallich 2012-06-20 16:07:42 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.