Version-Release number of selected component: telepathy-mission-control-5.15.0-2.fc21 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: g_logv executable: /usr/libexec/mission-control-5 kernel: 3.12.0-0.rc1.git2.2.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_logv at /lib/libglib-2.0.so.0 #1 g_log at /lib/libglib-2.0.so.0 #2 g_malloc at /lib/libglib-2.0.so.0 #3 g_strndup at /lib/libglib-2.0.so.0 #4 request_connection_cb #5 _tp_cli_connection_manager_invoke_callback_request_connection at /lib/libtelepathy-glib.so.0 #6 tp_proxy_pending_call_idle_invoke at /lib/libtelepathy-glib.so.0 #7 g_idle_dispatch at /lib/libglib-2.0.so.0 #8 g_main_context_dispatch at /lib/libglib-2.0.so.0 #9 g_main_context_iterate.isra.22 at /lib/libglib-2.0.so.0
Created attachment 800341 [details] File: backtrace
Created attachment 800342 [details] File: cgroup
Created attachment 800343 [details] File: core_backtrace
Created attachment 800344 [details] File: dso_list
Created attachment 800345 [details] File: environ
Created attachment 800346 [details] File: limits
Created attachment 800347 [details] File: maps
Created attachment 800348 [details] File: open_fds
Created attachment 800349 [details] File: proc_pid_status
Created attachment 800350 [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.