Version-Release number of selected component: telepathy-gabble-0.17.4-1.fc20 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: g_thread_new executable: /usr/libexec/telepathy-gabble kernel: 3.10.0-1.fc20.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_thread_new at gthread.c:839 #3 dconf_gdbus_get_worker_context at dconf-gdbus-thread.c:97 #4 dconf_engine_dbus_call_async_func at dconf-gdbus-thread.c:282 #5 dconf_engine_watch_fast at dconf-engine.c:766 #6 g_object_new_internal at gobject.c:1782 #7 g_object_new_valist at gobject.c:1999 #9 g_settings_new at gsettings.c:869 #10 g_proxy_resolver_gnome_init at gproxyresolvergnome.c:157 #11 g_type_create_instance at gtype.c:1868 #12 g_object_new_internal at gobject.c:1743
Created attachment 775400 [details] File: backtrace
Created attachment 775402 [details] File: cgroup
Created attachment 775403 [details] File: core_backtrace
Created attachment 775405 [details] File: dso_list
Created attachment 775407 [details] File: environ
Created attachment 775409 [details] File: limits
Created attachment 775410 [details] File: maps
Created attachment 775411 [details] File: open_fds
Created attachment 775412 [details] File: proc_pid_status
Created attachment 775413 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
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.
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.