Bug 687979 - [abrt] evolution-2.32.1-1.fc14: g_type_value_table_peek: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: g_type_value_table_peek: Process /usr/bin/evo...
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:f82cfe4a2cc408dd1e7d45e3b12...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 21:58 UTC by Kris Buytaert
Modified: 2011-03-16 06:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 06:46:02 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (57.85 KB, text/plain)
2011-03-15 21:58 UTC, Kris Buytaert 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Kris Buytaert 2011-03-15 21:58:34 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_type_value_table_peek
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 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Random Crash :( 
time: 1300226293
uid: 500
Comment 1 Kris Buytaert 2011-03-15 21:58:37 UTC 
Created attachment 485612 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-16 06:46:02 UTC 
Thanks for a bug report. There is filled a similar upstream bug [1], which contains a fix which is included in the 2.91.6 version of evolution-data-server, thus will be part of Fedora 15. I'm moving this to the upstream bug [1].

[1] https://bugzilla.gnome.org/show_bug.cgi?id=627788
Note You need to log in before you can comment on or make changes to this bug.