Hide Forgot
Version-Release number of selected component: telepathy-gabble-0.18.1-2.fc21 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: g_source_remove executable: /usr/libexec/telepathy-gabble kernel: 3.12.2-3.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_source_remove at /lib/libglib-2.0.so.0 #3 no_more_connections at /lib/libtelepathy-glib.so.0 #4 g_cclosure_marshal_VOID__VOIDv at /lib/libgobject-2.0.so.0 #5 _g_closure_invoke_va at /lib/libgobject-2.0.so.0 #8 connection_shutdown_finished_cb at /lib/libtelepathy-glib.so.0 #9 g_cclosure_marshal_VOID__VOIDv at /lib/libgobject-2.0.so.0 #10 _g_closure_invoke_va at /lib/libgobject-2.0.so.0 #13 tp_base_connection_finish_shutdown at /lib/libtelepathy-glib.so.0 #14 force_close_cb #15 g_simple_async_result_complete at /lib/libgio-2.0.so.0
Created attachment 832519 [details] File: backtrace
Created attachment 832520 [details] File: cgroup
Created attachment 832521 [details] File: core_backtrace
Created attachment 832522 [details] File: dso_list
Created attachment 832523 [details] File: environ
Created attachment 832524 [details] File: limits
Created attachment 832525 [details] File: maps
Created attachment 832526 [details] File: open_fds
Created attachment 832527 [details] File: proc_pid_status
Created attachment 832529 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.