Bug 705781 - [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 701321
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:79883d59af103e68a2c5538e94f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 12:49 UTC by Guilherme Rezende
Modified: 2011-05-19 06:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 06:22:47 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (104.81 KB, text/plain)
2011-05-18 12:50 UTC, Guilherme Rezende 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Guilherme Rezende 2011-05-18 12:49:59 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 107326 bytes
cmdline: evolution
comment: The same problem occurred with RHEL 6.
component: evolution
Attached file: coredump, 322019328 bytes
crash_function: mapi_mail_item_to_mime_message
executable: /usr/bin/evolution
kernel: 2.6.35.13-91.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305720971
uid: 500

How to reproduce
-----
1. The Evoluter has connected with the Exchange server through SSL
2. Started the download of the messages from the server
3. Crashed
Comment 1 Guilherme Rezende 2011-05-18 12:50:05 UTC 
Created attachment 499590 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-19 06:22:47 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 701321 ***
Note You need to log in before you can comment on or make changes to this bug.