Bug 144817

Summary:	evolution on x86_64 crashes when connecting to an exchange server
Product:	Red Hat Enterprise Linux 3	Reporter:	Ralph Smith <smith>
Component:	evolution-connector	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	rousseau, shillman
Target Milestone:	---	Keywords:	Desktop
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	RHEL3U7NAK
Fixed In Version:	RHBA-2006-0367	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-20 14:24:53 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:
Bug Blocks:	174536, 181405

Description Ralph Smith 2005-01-11 18:54:25 UTC

Description of problem:
evolution on x86_64 or intel EM64T crashes when doing transactions
with an Exchange server

Version-Release number of selected component (if applicable):
evolution-1.4.5-9
evolution-connector-1.4.7-5

How reproducible:
every time on specific system

Steps to Reproduce:
1. start up evolution
2. configure a mail folder for an existing account on an exchange server
3. click on the folder to initiate transaction
4. enter valid password in dialog box
  
Actual results:
crash message box

Expected results:
expanded list of folders on exchange server

Additional info:
You need to rebuild evolution using a newer version of binutils. 
(x86_64 relocation tables in shared libs are unreliable with the old
one.)  Also change "unsigned long" to guint32 in
ximian-exchange/camel/camel-stub.c

Comment 3 Dave Malcolm 2005-02-28 20:17:49 UTC

Thanks for this bug report.  I've gone through the uses of
CAMEL_STUB_ARG_UINT32 in the code and confirmed that it is actually
working on 32-bit values.

I'm applying a patch to fix the usage of unsigned long; I am trying to
get a fixed version into the next quarterly update.

Comment 16 Red Hat Bugzilla 2006-07-20 14:24:53 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0367.html