Bug 714679 - [abrt] evolution-2.32.2-1.fc14: resort_node: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: resort_node: Process /usr/bin/evolution was k...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ee2ed4fbcda598d0a2379f2f879...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 12:28 UTC by Miguel Angelo Mello
Modified: 2011-06-21 05:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 05:04:53 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (40.51 KB, text/plain)
2011-06-20 12:28 UTC, Miguel Angelo Mello
no flags Details


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

Description Miguel Angelo Mello 2011-06-20 12:28:22 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 41482 bytes
cmdline: /usr/bin/evolution
component: evolution
Attached file: coredump, 307527680 bytes
crash_function: resort_node
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1308568327
uid: 500

How to reproduce
-----
1. No specific action taken
2. Crash have happened on normal operation
3.

Comment 1 Miguel Angelo Mello 2011-06-20 12:28:27 UTC
Created attachment 505603 [details]
File: backtrace

Comment 2 Milan Crha 2011-06-21 05:04:53 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=653073


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