Description of problem: It likes to do this on startup. I just figured out how to report stuff caught by abrt but owned by somebody besides me. Version-Release number of selected component: telepathy-mission-control-5.14.1-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: g_slist_find executable: /usr/libexec/mission-control-5 kernel: 3.9.4-301.fc19.x86_64 runlevel: N 5 uid: 42 Truncated backtrace: Thread no. 1 (10 frames) #0 g_slist_find at gslist.c:727 #1 g_object_notify_queue_add at gobject.c:305 #2 object_set_property at gobject.c:1363 #3 g_object_constructor at gobject.c:1869 #4 dbus_g_proxy_constructor at dbus-gproxy.c:1429 #6 g_object_new_valist at gobject.c:1836 #8 dbus_g_proxy_new at dbus-gproxy.c:1992 #9 dbus_g_proxy_new_for_name at dbus-gproxy.c:2040 #10 tp_proxy_get_interface_by_id at proxy.c:502 #11 tp_proxy_borrow_interface_by_id at proxy.c:457
Created attachment 768531 [details] File: backtrace
Created attachment 768532 [details] File: cgroup
Created attachment 768533 [details] File: core_backtrace
Created attachment 768534 [details] File: dso_list
Created attachment 768535 [details] File: environ
Created attachment 768536 [details] File: limits
Created attachment 768537 [details] File: maps
Created attachment 768538 [details] File: open_fds
Created attachment 768539 [details] File: proc_pid_status
Created attachment 768540 [details] File: var_log_messages
This likes to happen on startup. The crashes happen in pairs, but with differing "killed by" signals. The pair to this one is Bug 956237. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 core_backtrace: crash_function: g_slist_find executable: /usr/libexec/mission-control-5 kernel: 3.9.5-301.fc19.x86_64 package: telepathy-mission-control-5.14.1-1.fc19 reason: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 42
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.