Bug 572465 - [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 564267
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-exchange
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a40ed50b54ee361a2e4ccf657e2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-11 09:54 UTC by Colin.Simpson
Modified: 2010-05-25 09:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:33:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (40.19 KB, text/plain)
2010-03-11 09:55 UTC, Colin.Simpson
no flags Details

Description Colin.Simpson 2010-03-11 09:54:58 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.28/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.28 --oaf-ior-fd=29
comment: Connecting to Exchange 2003
component: evolution-exchange
executable: /usr/libexec/evolution/2.28/evolution-exchange-storage
kernel: 2.6.31.12-174.2.22.fc12.x86_64
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. Just started evolution normally and despite being updated crashed straight away
2. restarting Evolution brings it back to life.
3.

Comment 1 Colin.Simpson 2010-03-11 09:55:01 UTC
Created attachment 399302 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:33:59 UTC

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

Comment 3 Karel Klíč 2010-05-25 09:33:59 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 #564267.

Sorry for the inconvenience.


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