Bug 200563 – freetype-2.1.9-1.rhel4.4 crashes evolution-2.0.2-27

Bug 200563 - freetype-2.1.9-1.rhel4.4 crashes evolution-2.0.2-27

Summary:	freetype-2.1.9-1.rhel4.4 crashes evolution-2.0.2-27

Status:	CLOSED DUPLICATE of bug 200033

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	freetype (Show other bugs)
Sub Component:
Version:	4.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Behdad Esfahbod
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-07-28 13:50 EDT by Stephen Murray
Modified:	2007-11-30 17:07 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-07-30 15:10:47 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Stephen Murray 2006-07-28 13:50:59 EDT

Description of problem:

After updating to freetype-2.1.9-1.rhel4.4, evolution-2.0.2-27 crashes during
startup. Deleting directory $HOME/.evolution allows evolution to start, but it
crashes after looking at a few mail messages. Evolution is configured to use
IMAP. Evolution on Fedora Core 5 and SUSE 10.1 RCx, running against the same
mail server/account, does not crash. Updating to evolution-2.0.4-7 (from FC3)
does not resolve the issue. Restoring to prior version freetype-2.1.9-1 resolves
the issue.

Version-Release number of selected component (if applicable):

freetype-2.1.9-1.rhel4.4, evolution-2.0.2-27, evolution-2.0.4-7

How reproducible:
Install freetype-2.1.9-1.rhel4.4, start evolution.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

evolution crash

Expected results:

access mail account

Additional info:

Restoring to prior version freetype-2.1.9-1 resolves the issue.

Comment 1 Behdad Esfahbod 2006-07-30 15:10:47 EDT

This is fixed already.

*** This bug has been marked as a duplicate of 200033 ***

Note You need to log in before you can comment on or make changes to this bug.