Bug 594424 - [abrt] crash in evolution-data-server-2.30.1-2.fc13: raise: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-data-server-2.30.1-2.fc13: raise: Process /usr/libe...
Keywords:
Status: CLOSED DUPLICATE of bug 629263
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1cb6c62d823043413d11d5b145a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-20 16:09 UTC by Mat Booth
Modified: 2010-11-09 14:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:16:15 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (29.87 KB, text/plain)
2010-05-20 16:09 UTC, Mat Booth 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Mat Booth 2010-05-20 16:09:18 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
comment: New email->Clicked "To"->Looked through the list of contacts.
component: evolution-data-server
crash_function: raise
executable: /usr/libexec/e-addressbook-factory
global_uuid: 1cb6c62d823043413d11d5b145a30307e23a8466
kernel: 2.6.33.3-79.fc13.i686
package: evolution-data-server-2.30.1-2.fc13
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Mat Booth 2010-05-20 16:09:21 UTC 
Created attachment 415461 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:16:15 UTC 

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

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