Bug 681177 - [abrt] evolution-2.32.1-1.fc14: g_type_check_instance_cast: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: g_type_check_instance_cast: Process /usr/bin/...
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:ef47e9bc6d2cfb764d670a6afe8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-01 11:23 UTC by Incog Nito
Modified: 2011-03-02 07:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-02 07:20:38 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (60.63 KB, text/plain)
2011-03-01 11:23 UTC, Incog Nito
no flags Details


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

Description Incog Nito 2011-03-01 11:23:09 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 62086 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 117219328 bytes
crash_function: g_type_check_instance_cast
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.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: 1298967673
uid: 500

How to reproduce
-----
1. opened evolution
2.connected to exchange server via https
3. crash occured

Comment 1 Incog Nito 2011-03-01 11:23:12 UTC
Created attachment 481595 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-02 07:20:38 UTC
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. 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=625018


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