Bug 683424

Summary: [abrt] evolution-data-server-2.32.2-1.fc14: magazine_chain_pop_head: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David <david.m.beer>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX 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:889f25fa8d8b361e5c098d84d2f31e383cb2fe2c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:16:27 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

Description David 2011-03-09 11:59:20 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 43382 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 48148480 bytes
crash_function: magazine_chain_pop_head
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299671760
uid: 500

How to reproduce
-----
1. Creating a new appointment in the calendar part of evolution
2.
3.

Comment 1 David 2011-03-09 11:59:23 UTC
Created attachment 483172 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-09 12:24:03 UTC
Thanks for a bug report. I see it failed to allocate 72 bytes when opening an EBookBackend, which doesn't mean much. There are two threads trying to open that backend, one is operating (crashing, in our case), the other is waiting on the first to finish. Books are opened due to meetings in calendar view, though they are opened even for regular appointments. Was this just a "random" crash? ("random" here means a "very hard to reproduce").

Comment 3 David 2011-03-09 13:18:27 UTC
Yes I would call this random. Although I have had this come up a few time. I am wondering if it is because my main calendar component is set to a google calendar. And if there is an issue connecting to it, it throws a fit and crashes.

This is the only thing I can think of in my setup that might cause an error.

Comment 4 Milan Crha 2011-03-10 07:23:01 UTC
It might not be due to calendar, because calendar is in e-calendar-factory, and for you is crashing e-addressbook-factory. I'm afraid that even valgrind may not help here, as it's not always reproducible.

I've no idea what to try next.

Comment 5 Fedora End Of Life 2012-08-16 14:16:32 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping