Bug 701148

Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_type_check_instance_cast: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Peque <msdeleonpeque>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0419f9abefc6f5bf4b0800d65690842ad14ec404
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-02 14:25:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
Backtrace for crash of evolution-data-server none

Description Peque 2011-05-01 15:31:43 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 24616 bytes
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
Attached file: coredump, 28405760 bytes
crash_function: g_type_check_instance_cast
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.12-88.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Don't know how this happened...
time: 1304217273
uid: 500
Comment 1 Peque 2011-05-01 15:31:46 UTC 
Created attachment 496068 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-02 06:03:43 UTC 
Thanks for a bug report. I see you do not know how this happened, and from the backtrace I cannot read it too. Is it some kind of an occasion crash, which happens from time to time? You know, the backtrace doesn't give enough information to identify the issue (this is not about debugging symbol, those are OK; this is rather about understanding what happened that it crashed this way) and without a reproducer it's also not quite possible to fix the root cause of this.
Comment 3 Peque 2011-05-02 14:06:11 UTC 
Sorry, but I can't provide any further information... This crash happened just once, and I think I was opening a PDF (which I guess it has nothing to do with the crash). I tried to reproduce it opening the same PDF file but, of course, I couldn't...

Anyway, thanks for your effort :-).
Comment 4 Milan Crha 2011-05-02 14:25:33 UTC 
Thanks for the update. You've right that the PDF file opening is most likely unrelated, unless the reader does some memory corruption with writing in a memory which doesn't belong to it, but I may not expect anything like that.

I'm closing this, but please feel free to reopen this one or file new bug reports, if you face any.
Comment 5 Noel Duffy 2012-03-17 23:20:56 UTC 
Created attachment 570849 [details]
Backtrace for crash of evolution-data-server

This is the backtrace of one of my now increasingly frequent crashes of evolution-data-server. This crash happened when I logged out and back in again after having wireless connectivity troubles. The crash always seems to happen on login.
Comment 6 Milan Crha 2012-03-19 12:49:31 UTC 
Thanks for the update, Noel. I cannot recognize from the backtrace, thus I'm rather asking, what is your evolution version, please? I do not recall seeing any similar crash from Fedora 16, and the upcoming Fedora 17 may have this fixed as well.