Version-Release number of selected component: telepathy-salut-0.8.1-7.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-salut crash_function: _g_log_abort executable: /usr/libexec/telepathy-salut global_pid: 31694 kernel: 4.1.6-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #3 g_source_remove at gmain.c:2252 #4 gibber_oob_file_transfer_finalize at gibber-oob-file-transfer.c:117 #6 salut_file_transfer_channel_dispose at file-transfer-channel.c:750 #8 g_value_unset at gvalue.c:272 #9 g_value_array_free at gvaluearray.c:169 #10 invoke_object_method at dbus-gobject.c:2049 #11 object_registration_message at dbus-gobject.c:2168 #12 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:1018 #19 tp_run_connection_manager at run.c:284
Created attachment 1070876 [details] File: backtrace
Created attachment 1070877 [details] File: cgroup
Created attachment 1070878 [details] File: core_backtrace
Created attachment 1070879 [details] File: dso_list
Created attachment 1070880 [details] File: environ
Created attachment 1070881 [details] File: limits
Created attachment 1070882 [details] File: maps
Created attachment 1070883 [details] File: mountinfo
Created attachment 1070884 [details] File: namespaces
Created attachment 1070885 [details] File: open_fds
Created attachment 1070886 [details] File: proc_pid_status
Created attachment 1070887 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.