Bug 670433 - [abrt] evolution-2.32.1-1.fc14: e_tree_get_cursor: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: e_tree_get_cursor: Process /usr/bin/evolution...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:55987d219fe41d45f80f5d880ec...
: 691408 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 09:47 UTC by John Kissane
Modified: 2011-03-29 05:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-19 08:47:22 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (47.13 KB, text/plain)
2011-01-18 09:48 UTC, John Kissane
no flags Details


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

Description John Kissane 2011-01-18 09:47:58 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: e_tree_get_cursor
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295343937
uid: 2283

How to reproduce
-----
1. Deleted an email
2.
3.

Comment 1 John Kissane 2011-01-18 09:48:01 UTC
Created attachment 474012 [details]
File: backtrace

Comment 2 Milan Crha 2011-01-19 08:47:22 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=639926

Comment 3 Milan Crha 2011-03-29 05:50:38 UTC
*** Bug 691408 has been marked as a duplicate of this bug. ***


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