Bug 1090215

Summary: [abrt] Crash under dconf_gdbus_worker_thread()
Product: [Fedora] Fedora Reporter: ural.spence
Component: dconfAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, mbarnes, mclasen, mcrha, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8a11b12c49c2083d9a0849fca55489d887d4171f
Whiteboard: abrt_hash:976e457b5b10a93ccbab53c0fd7ddc15d5862b23
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:14:44 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 ural.spence 2014-04-23 00:44:18 UTC 
Description of problem:
Not sure

Version-Release number of selected component:
evolution-data-server-3.10.2-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 3
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: g_type_check_instance
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance at gtype.c:4080
 #1 g_signal_handler_disconnect at gsignal.c:2580
 #2 on_connection_disconnected at gdbusnamewatching.c:260
 #3 ffi_call_unix64 at ../src/x86/unix64.S:76
 #4 ffi_call at ../src/x86/ffi64.c:522
 #5 g_cclosure_marshal_generic at gclosure.c:1454
 #10 emit_closed_in_idle at gdbusconnection.c:1389
 #14 g_main_context_iteration at gmain.c:3774
 #15 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81
 #16 g_thread_proxy at gthread.c:798
Comment 1 ural.spence 2014-04-23 00:44:28 UTC 
Created attachment 888687 [details]
File: backtrace
Comment 2 ural.spence 2014-04-23 00:44:32 UTC 
Created attachment 888688 [details]
File: cgroup
Comment 3 ural.spence 2014-04-23 00:44:40 UTC 
Created attachment 888689 [details]
File: core_backtrace
Comment 4 ural.spence 2014-04-23 00:44:47 UTC 
Created attachment 888690 [details]
File: dso_list
Comment 5 ural.spence 2014-04-23 00:44:51 UTC 
Created attachment 888691 [details]
File: environ
Comment 6 ural.spence 2014-04-23 00:44:56 UTC 
Created attachment 888692 [details]
File: exploitable
Comment 7 ural.spence 2014-04-23 00:45:02 UTC 
Created attachment 888693 [details]
File: limits
Comment 8 ural.spence 2014-04-23 00:45:24 UTC 
Created attachment 888694 [details]
File: maps
Comment 9 ural.spence 2014-04-23 00:45:28 UTC 
Created attachment 888695 [details]
File: open_fds
Comment 10 ural.spence 2014-04-23 00:45:32 UTC 
Created attachment 888696 [details]
File: proc_pid_status
Comment 11 ural.spence 2014-04-23 00:45:36 UTC 
Created attachment 888697 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-04-23 14:35:09 UTC 
Thanks for a bug report. I'm also not sure what could cause the trouble, the only thing I see is that the evolution-source-registry was probably closing itself, while the dconf_gdbus_worker_thread recognized a disconnect from a related D-Bus service and it tried to react on it. It is most likely accessing already freed memory, thus it caused a crash.

I guess this was more like a one-time crash, right?

I'm reassigning this to dconf anyway, to check whether they disconnect themself from the GDBusConnection on the dispose, thus the signal callback is not invoked on the already freed object.
Comment 13 Fedora End Of Life 2015-05-29 11:39:01 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 14 Fedora End Of Life 2015-06-29 20:14:44 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.