Bug 767437

Summary: [abrt] evolution-data-server-3.2.2-1.fc16: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Louis van Dyk <louis>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b14f5f20707bf1863911dc4439e9fc2dbaff2fa5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-14 07:26:46 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: dso_list
none
File: maps
none
File: smolt_data
none
File: backtrace none

Description Louis van Dyk 2011-12-14 02:43:27 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        /usr/libexec/e-calendar-factory
comment:        My calendar has never updated since connecting to the exchange server with evolution-ews.  I have left it open for ages.  I can send mail using my mail account.  Three lines appear under my address heading in the calendar view.  They say "BCX", "Calendar" and again "Calendar".  I un-ticked the boxes, waited 5 seconds, then ticked them again.  At that moment the calendar crash appeared.
crash_function: e_ews_connection_sync_folder_items_start
executable:     /usr/libexec/e-calendar-factory
kernel:         3.1.2-1.fc16.x86_64
pid:            3618
pwd:            /
reason:         Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
time:           Wed 14 Dec 2011 04:29:59 AM SAST
uid:            1000
username:       louis
var_log_messages: Dec 14 04:30:00 fedora abrt[20195]: Saved core dump of pid 3618 (/usr/libexec/e-calendar-factory) to /var/spool/abrt/ccpp-2011-12-14-04:29:59-3618 (56483840 bytes)

backtrace:      Text file, 31495 bytes
dso_list:       Text file, 8894 bytes
maps:           Text file, 39674 bytes
smolt_data:     Text file, 2692 bytes

environ:
:SHELL=/bin/bash
:DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-WERelj4N8Z,guid=05e6eeaf66f2e4d8a0804ae700000024
:XDG_SESSION_COOKIE=7075619d19a1b86ee0cf10000000000d-1323015503.204572-1840091069
:XDG_RUNTIME_DIR=/run/user/louis
:DISPLAY=:0
:DESKTOP_SESSION=gnome
:SSH_AUTH_SOCK=/tmp/keyring-3M7n6i/ssh
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1478,unix/unix:/tmp/.ICE-unix/1478
:WINDOWPATH=1
:PATH=/usr/local/bin:/usr/bin:/bin
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:GDMSESSION=gnome
:XDG_VTNR=1
:USERNAME=louis
:XDG_SESSION_ID=2
:GPG_AGENT_INFO=/tmp/keyring-3M7n6i/gpg:0:1
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-WERelj4N8Z,guid=05e6eeaf66f2e4d8a0804ae700000024
:XDG_SEAT=seat0
:XAUTHORITY=/var/run/gdm/auth-for-louis-LdHh28/database
:USER=louis
:DBUS_STARTER_BUS_TYPE=session
:GNOME_KEYRING_PID=1474
:SHLVL=1
:PWD=/home/louis
:GNOME_KEYRING_CONTROL=/tmp/keyring-3M7n6i
:LANG=en_US.UTF-8
:_=/usr/bin/dbus-launch
:LOGNAME=louis
:HOME=/home/louis
Comment 1 Louis van Dyk 2011-12-14 02:43:31 UTC 
Created attachment 546502 [details]
File: dso_list
Comment 2 Louis van Dyk 2011-12-14 02:43:34 UTC 
Created attachment 546503 [details]
File: maps
Comment 3 Louis van Dyk 2011-12-14 02:43:37 UTC 
Created attachment 546504 [details]
File: smolt_data
Comment 4 Louis van Dyk 2011-12-14 02:43:40 UTC 
Created attachment 546505 [details]
File: backtrace
Comment 5 Milan Crha 2011-12-14 07:26:46 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=661979