Bug 600910 - [abrt] crash in evolution-2.30.1-8.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-2.30.1-8.fc13: raise: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED DUPLICATE of bug 641750
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6b4af1b4c31d6d1a5f27cc59f24...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-06 16:34 UTC by Boricua
Modified: 2010-11-09 13:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:09:31 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (99.30 KB, text/plain)
2010-06-06 16:34 UTC, Boricua 		no flags Details
View All

Description Boricua 2010-06-06 16:34:49 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: It might be a coincidence, but jsut in case I report running gpilot sync before after that I opened Evolution and the crash took place.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 6b4af1b4c31d6d1a5f27cc59f248021371f2a6d0
kernel: 2.6.33.5-112.fc13.x86_64
package: evolution-2.30.1-8.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Run gpilot sync
2.Start Evolution
3.Evolution crashes
Comment 1 Boricua 2010-06-06 16:34:53 UTC 
Created attachment 421619 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:09:31 UTC 

*** This bug has been marked as a duplicate of bug 641750 ***
Comment 3 Karel Klíč 2010-11-09 13:09:31 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 #641750.

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