Bug 638280 - [abrt] evolution-2.30.3-1.fc13: talloc_abort: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-2.30.3-1.fc13: talloc_abort: Process /usr/bin/evolution was ...
Keywords:
Status: CLOSED DUPLICATE of bug 631873
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3936419973cf3153caf6d05a590...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-28 16:28 UTC by mark
Modified: 2010-11-09 15:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:56:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.39 KB, text/plain)
2010-09-28 16:28 UTC, mark
no flags Details

Description mark 2010-09-28 16:28:05 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: talloc_abort
executable: /usr/bin/evolution
kernel: 2.6.34.6-54.fc13.i686
package: evolution-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1284573506
uid: 500

comment
-----
tried to use evoultion with the map connector.

this is the 4th bug report for the various ways to crash evolultion, I will keep reporting these to the black hole. 

How to reproduce
-----
1. let evolution sync mail to my local machine rather than pull it off the exhchange server
2. use mapi connector. 
3. watch it self kill.

Comment 1 mark 2010-09-28 16:28:07 UTC
Created attachment 450241 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:56:46 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:56: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 #631873.

Sorry for the inconvenience.


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