Bug 585914 - [abrt] crash in evolution-data-server-2.28.3-2.fc12: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-data-server-2.28.3-2.fc12: Process /usr/libexec/evo...
Keywords:
Status: CLOSED DUPLICATE of bug 565937
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ceb01563e88c18f22b27f997fd1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 12:16 UTC by roberto agria
Modified: 2010-05-24 15:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-24 15:05:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (36.80 KB, text/plain)
2010-04-26 12:16 UTC, roberto agria
no flags Details

Description roberto agria 2010-04-26 12:16:24 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=26
component: evolution-data-server
executable: /usr/libexec/evolution-data-server-2.28
global_uuid: ceb01563e88c18f22b27f997fd16d3d29a537999
kernel: 2.6.32.11-99.fc12.i686.PAE
package: evolution-data-server-2.28.3-2.fc12
rating: 4
reason: Process /usr/libexec/evolution-data-server-2.28 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 roberto agria 2010-04-26 12:16:27 UTC
Created attachment 409162 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-24 15:05:43 UTC

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

Comment 3 Karel Klíč 2010-05-24 15:05:43 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 #565937.

Sorry for the inconvenience.


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