Bug 675729 - [abrt] evolution-2.32.1-1.fc14: __libc_message: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-2.32.1-1.fc14: __libc_message: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:002290b6e5a36165f35cd0963d1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 14:50 UTC by Allan Wright
Modified: 2011-02-08 10:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-08 10:51:51 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (39.99 KB, text/plain)
2011-02-07 14:50 UTC, Allan Wright 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 641821 0 None None None Never

Description Allan Wright 2011-02-07 14:50:12 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Was trying to expunge a folder and Evolution crashed
component: evolution
crash_function: __libc_message
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.fc14.i686
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297090101
uid: 20084

How to reproduce
-----
1. <CTL>A
2.<CTL>E
3.Evolution crashed
Comment 1 Allan Wright 2011-02-07 14:50:14 UTC 
Created attachment 477425 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-08 10:51:51 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=641821
Note You need to log in before you can comment on or make changes to this bug.