Bug 690411

Summary: [abrt] evolution-2.32.2-1.fc14: talloc_abort: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Cyril Sluchanko <bugzilla.10.cyrils>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:68f5158428324e1348d4dea03f53561bc12d0dfc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-28 07:11:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Cyril Sluchanko 2011-03-24 09:49:01 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 48759 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 1601994752 bytes
crash_function: talloc_abort
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300941856
uid: 16777216

How to reproduce
-----
1. No actions were performed by user.
2.
3.
Comment 1 Cyril Sluchanko 2011-03-24 09:49:03 UTC 
Created attachment 487269 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-28 07:11:43 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=645899
Comment 3 Milan Crha 2011-03-28 07:12:26 UTC 
*** Bug 690747 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2011-05-06 07:29:11 UTC 
*** Bug 702341 has been marked as a duplicate of this bug. ***