Bug 600874 - [abrt] crash in evolution-2.30.1-6.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in evolution-2.30.1-6.fc13: raise: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED DUPLICATE of bug 584960
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:7b36e815fc25fa38c28213d4dd5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-06 12:54 UTC by brizly vaan van Ulciputz
Modified: 2010-11-08 19:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:45:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (34.04 KB, text/plain)
2010-06-06 12:54 UTC, brizly vaan van Ulciputz
no flags Details

Description brizly vaan van Ulciputz 2010-06-06 12:54:05 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: i did nothing special, evolution was running in background. after lunch ABRT-alert was in 'systray'.
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 7b36e815fc25fa38c28213d4dd574ed2a24bcf47
kernel: 2.6.33.5-112.fc13.x86_64
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. don't know how to reproduce

Comment 1 brizly vaan van Ulciputz 2010-06-06 12:54:07 UTC
Created attachment 421591 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:45:46 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:45:46 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 #584960.

Sorry for the inconvenience.


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