Bug 144817 - evolution on x86_64 crashes when connecting to an exchange server
evolution on x86_64 crashes when connecting to an exchange server
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: evolution-connector (Show other bugs)
3.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
RHEL3U7NAK
: Desktop
Depends On:
Blocks: 174536 RHEL3U8CanFix
  Show dependency treegraph
 
Reported: 2005-01-11 13:54 EST by Ralph Smith
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2006-0367
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-20 10:24:53 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)

  None (edit)
Description Ralph Smith 2005-01-11 13:54:25 EST
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 15:17:49 EST
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 10:24:53 EDT
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

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