Bug 1231902

Summary: [abrt] evolution-data-server: g_type_check_instance(): evolution-addressbook-factory-subprocess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ferry Huberts <mailings>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: HolyMaster, JDP803, louis, mbarnes, mcrha, nicolas.laplante, rnfano2
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/af554f5e224b7dbb3e0d3e8ed9f3ae35cb4362cc
Whiteboard: abrt_hash:976e457b5b10a93ccbab53c0fd7ddc15d5862b23
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 13:46: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:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description Ferry Huberts 2015-06-15 15:02:24 UTC 
Version-Release number of selected component:
evolution-data-server-3.16.2-2.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-addressbook-factory-subprocess --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx3184x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/3184/2
crash_function: g_type_check_instance
executable:     /usr/libexec/evolution-addressbook-factory-subprocess
global_pid:     3207
kernel:         4.0.4-303.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Tue 2014-12-09 08:40:47 CET, end at Sat 2015-06-06 16:48:32 CEST. --

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 g_type_check_instance at gtype.c:4134
 #1 g_signal_handler_disconnect at gsignal.c:2556
 #2 on_connection_disconnected at gdbusnameowning.c:405
 #3 ffi_call_unix64 at ../src/x86/unix64.S:76
 #4 ffi_call at ../src/x86/ffi64.c:525
 #5 g_cclosure_marshal_generic at gclosure.c:1448
 #10 emit_closed_in_idle at gdbusconnection.c:1386
 #15 source_registry_object_manager_thread at e-source-registry.c:1160
 #16 g_thread_proxy at gthread.c:764
Comment 1 Ferry Huberts 2015-06-15 15:02:27 UTC 
Created attachment 1039105 [details]
File: backtrace
Comment 2 Ferry Huberts 2015-06-15 15:02:29 UTC 
Created attachment 1039106 [details]
File: cgroup
Comment 3 Ferry Huberts 2015-06-15 15:02:30 UTC 
Created attachment 1039107 [details]
File: core_backtrace
Comment 4 Ferry Huberts 2015-06-15 15:02:32 UTC 
Created attachment 1039108 [details]
File: dso_list
Comment 5 Ferry Huberts 2015-06-15 15:02:33 UTC 
Created attachment 1039109 [details]
File: environ
Comment 6 Ferry Huberts 2015-06-15 15:02:35 UTC 
Created attachment 1039110 [details]
File: limits
Comment 7 Ferry Huberts 2015-06-15 15:02:36 UTC 
Created attachment 1039111 [details]
File: maps
Comment 8 Ferry Huberts 2015-06-15 15:02:38 UTC 
Created attachment 1039112 [details]
File: mountinfo
Comment 9 Ferry Huberts 2015-06-15 15:02:40 UTC 
Created attachment 1039113 [details]
File: namespaces
Comment 10 Ferry Huberts 2015-06-15 15:02:41 UTC 
Created attachment 1039114 [details]
File: open_fds
Comment 11 Ferry Huberts 2015-06-15 15:02:43 UTC 
Created attachment 1039115 [details]
File: proc_pid_status
Comment 12 Milan Crha 2015-06-16 05:04:21 UTC 
Thanks for a bug report. There had been filled more or less similar bug reports in the past, namely bug #1172229 and bug #1180540, but none had any solution. The circumstances of the crash are also rather unknown. Do you know what you were doing when the crash happened, please? Based on the backtrace, maybe an evolution-source-registry process was closed unexpectedly?
Comment 13 Ferry Huberts 2015-06-16 06:41:08 UTC 
Could be.
I don't use evolution and when it opens because I tried to close a notification but failed at it, I usually close it very fast, uttering a curse ;-)
Comment 14 Milan Crha 2016-03-30 11:22:39 UTC 
*** Bug 1319464 has been marked as a duplicate of this bug. ***
Comment 15 Milan Crha 2016-04-12 12:13:24 UTC 
*** Bug 1326134 has been marked as a duplicate of this bug. ***
Comment 16 Fedora End Of Life 2016-11-24 11:53:55 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 17 Fedora End Of Life 2016-12-20 13:46:46 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.