Bug 579663 - [abrt] crash in evolution-exchange-2.28.3-1.fc12: Process /usr/libexec/evolution/2.28/evolution-exchange-storage was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-exchange-2.28.3-1.fc12: Process /usr/libexec/evolut...
Keywords:
Status: CLOSED DUPLICATE of bug 593007
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-exchange
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c130f39a3b267eca45741d81345...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-06 07:43 UTC by Emil Styrke
Modified: 2010-05-25 08:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:23:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.53 KB, text/plain)
2010-04-06 07:43 UTC, Emil Styrke 		no flags Details
View All

Description Emil Styrke 2010-04-06 07:43:47 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.28/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_BookFactory:1.2 --oaf-ior-fd=36
comment: Evolution keeps working, but all operations against the exchange account fail.
component: evolution-exchange
executable: /usr/libexec/evolution/2.28/evolution-exchange-storage
kernel: 2.6.32.10-90.fc12.i686.PAE
package: evolution-exchange-2.28.3-1.fc12
rating: 4
reason: Process /usr/libexec/evolution/2.28/evolution-exchange-storage was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Start Evolution
2. Crash (a few seconds after main window shows).
3.
Comment 1 Emil Styrke 2010-04-06 07:43:50 UTC 
Created attachment 404638 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:23:26 UTC 

*** This bug has been marked as a duplicate of bug 593007 ***
Comment 3 Karel Klíč 2010-05-25 08:23:26 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #593007.

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