Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 591825 - [abrt] crash in evolution-2.28.3-1.fc12: message_info_to_db: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.28.3-1.fc12: message_info_to_db: Process /usr/bin...
Status: CLOSED DUPLICATE of bug 556240
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:3371126ca0ef5ac181e2af3241a...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-13 09:48 UTC by Nuno Dias
Modified: 2010-05-24 15:05 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (62.18 KB, text/plain)
2010-05-13 09:48 UTC, Nuno Dias
no flags Details

Description Nuno Dias 2010-05-13 09:48:38 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Simple move a message from inbox to other folder
component: evolution
crash_function: message_info_to_db
executable: /usr/bin/evolution
global_uuid: 3371126ca0ef5ac181e2af3241a77cbbf8d70de8
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce

Comment 1 Nuno Dias 2010-05-13 09:48:41 UTC
Created attachment 413698 [details]
File: backtrace

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

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

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

Sorry for the inconvenience.

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