Bug 621270 - [abrt] crash in evolution-2.30.2-4.fc13: camel_object_cast: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-4.fc13: camel_object_cast: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 632098
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:6bdd12f830a4d3b93242828d1d9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-04 16:03 UTC by Torbjørn Lindahl
Modified: 2010-11-09 13:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:30:53 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.14 KB, text/plain)
2010-08-04 16:03 UTC, Torbjørn Lindahl 		no flags Details
View All

Description Torbjørn Lindahl 2010-08-04 16:03:38 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: not sure why it crashed (again). these crashes happen every single day. I just keep reporting hoping that things will improve.
component: evolution
crash_function: camel_object_cast
executable: /usr/bin/evolution
global_uuid: 6bdd12f830a4d3b93242828d1d944598d0dbf378
kernel: 2.6.33.6-147.fc13.x86_64
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. not sure, just reading my OWA account emails
2.
3.
Comment 1 Torbjørn Lindahl 2010-08-04 16:03:41 UTC 
Created attachment 436588 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:30:53 UTC 

*** This bug has been marked as a duplicate of bug 632098 ***
Comment 3 Karel Klíč 2010-11-09 13:30:53 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 #632098.

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