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.3-1.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 new_connection at /lib/libtelepathy-glib.so.0 #4 ffi_call_SYSV at /lib/libffi.so.6 #5 ffi_call at /lib/libffi.so.6 #6 g_cclosure_marshal_generic at /lib/libgobject-2.0.so.0 #11 tp_svc_connection_manager_emit_new_connection at /lib/libtelepathy-glib.so.0 #12 tp_base_connection_manager_request_connection at /lib/libtelepathy-glib.so.0 #13 tp_svc_connection_manager_request_connection at /lib/libtelepathy-glib.so.0 #14 ffi_call_SYSV at /lib/libffi.so.6 #15 ffi_call at /lib/libffi.so.6
Created attachment 833575 [details] File: backtrace
Created attachment 833576 [details] File: cgroup
Created attachment 833577 [details] File: core_backtrace
Created attachment 833578 [details] File: dso_list
Created attachment 833579 [details] File: environ
Created attachment 833580 [details] File: limits
Created attachment 833581 [details] File: maps
Created attachment 833582 [details] File: open_fds
Created attachment 833583 [details] File: proc_pid_status
Created attachment 833584 [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.