Bug 1180540

Summary: [abrt] evolution-data-server: g_dbus_connection_signal_unsubscribe(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Rolle <rolle.hoffmann>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: mbarnes, mcrha, rolle.hoffmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0196a8a08bae56021f95ae1e4cf9c41e89f67b92
Whiteboard: abrt_hash:3217cb0fe83cbe350764f9edf445af0c00769304
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-04 14:28:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Rolle 2015-01-09 12:10:56 UTC 
Version-Release number of selected component:
evolution-data-server-3.12.8-2.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: g_dbus_connection_signal_unsubscribe
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.17.4-301.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 g_dbus_connection_signal_unsubscribe at gdbusconnection.c:3670
 #1 on_connection_disconnected at gdbusnamewatching.c:258
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
 #4 g_cclosure_marshal_generic at gclosure.c:1448
 #9 emit_closed_in_idle at gdbusconnection.c:1386
 #13 g_main_context_iteration at gmain.c:3842
 #14 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:82
 #15 g_thread_proxy at gthread.c:764
Comment 1 Rolle 2015-01-09 12:10:59 UTC 
Created attachment 978109 [details]
File: backtrace
Comment 2 Rolle 2015-01-09 12:11:00 UTC 
Created attachment 978110 [details]
File: cgroup
Comment 3 Rolle 2015-01-09 12:11:02 UTC 
Created attachment 978111 [details]
File: core_backtrace
Comment 4 Rolle 2015-01-09 12:11:03 UTC 
Created attachment 978112 [details]
File: dso_list
Comment 5 Rolle 2015-01-09 12:11:04 UTC 
Created attachment 978113 [details]
File: environ
Comment 6 Rolle 2015-01-09 12:11:06 UTC 
Created attachment 978114 [details]
File: exploitable
Comment 7 Rolle 2015-01-09 12:11:07 UTC 
Created attachment 978115 [details]
File: limits
Comment 8 Rolle 2015-01-09 12:11:08 UTC 
Created attachment 978116 [details]
File: maps
Comment 9 Rolle 2015-01-09 12:11:09 UTC 
Created attachment 978117 [details]
File: open_fds
Comment 10 Rolle 2015-01-09 12:11:11 UTC 
Created attachment 978118 [details]
File: proc_pid_status
Comment 11 Rolle 2015-01-09 12:11:12 UTC 
Created attachment 978119 [details]
File: var_log_messages
Comment 12 Milan Crha 2015-01-26 17:49:08 UTC 
Thanks for a bug report. The crashing thread is fully dconf's, evolution's code doesn't use it directly. It can be that this happened due to some incorrect usage of "a common" memory by evolution, but that's something I cannot properly guess from the backtrace.

On the other hand evolution-data-server 3.12.8 had an issue which could eventually cause similar crashers. Could you update to the most recent version of evolution packages (3.12.10), please? They contain fixes which should help here. Thanks in advance.
Comment 13 Rolle 2015-02-02 09:49:37 UTC 
I installed all updates now (including evolution packages (3.12.10)). I don't know anymore what I did to lead to the crash. So I can't verify if this solves the problem.
Comment 14 Milan Crha 2015-02-04 14:28:38 UTC 
Thanks for the update. I'm closing this for now, due to lack of a reproducer, but please feel free to reopen or file new bugs, if you get any information with respect of the reproducer and circumstances which would lead to such crash.