Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 592065 - [abrt] crash in evolution-2.28.3-1.fc12: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] crash in evolution-2.28.3-1.fc12: raise: Process /usr/bin/evolution wa...
Status: CLOSED DUPLICATE of bug 563701
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-13 15:14 EDT by b_alary
Modified: 2010-05-25 05:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 05:21:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (51.38 KB, text/plain)
2010-05-13 15:14 EDT, b_alary
no flags Details

  None (edit)
Description b_alary 2010-05-13 15:14:18 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution --sm-config-prefix /evolution-h2iG1c/ --sm-client-id 105832d8b2332b16ef127317546295009300000016470036 --screen 0
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: bba6da466afab8c5e8b85e19834351e60dfb9516
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 b_alary 2010-05-13 15:14:22 EDT
Created attachment 413865 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:21:06 EDT

*** This bug has been marked as a duplicate of bug 563701 ***
Comment 3 Karel Klíč 2010-05-25 05:21:06 EDT
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 #563701.

Sorry for the inconvenience.

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