Description of problem: just booted and logged into gnome3 Version-Release number of selected component: telepathy-mission-control-5.14.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.7.0-0.rc7.git3.2.fc19.x86_64 remote_result: NOTFOUND uid: 42 var_log_messages: Dec 5 14:49:45 quadvadis abrt[13238]: Saved core dump of pid 13230 (/usr/libexec/mission-control-5) to /var/spool/abrt/ccpp-2012-12-05-14:49:45-13230 (1458176 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:532 #1 thread_memory_magazine1_alloc at gslice.c:835 #2 g_slice_alloc at gslice.c:994 #3 g_mutex_new at deprecated/gthread-deprecated.c:1472 #4 g_static_mutex_get_mutex_impl at deprecated/gthread-deprecated.c:529 #6 dbus_g_proxy_manager_register at dbus-gproxy.c:934 #7 dbus_g_proxy_constructor at dbus-gproxy.c:1444 #9 g_object_new_valist at gobject.c:1835 #11 dbus_g_proxy_new at dbus-gproxy.c:1992 #12 dbus_g_proxy_new_for_name at dbus-gproxy.c:2040
Created attachment 658234 [details] File: backtrace
Created attachment 658236 [details] File: cgroup
Created attachment 658239 [details] File: core_backtrace
Created attachment 658241 [details] File: dso_list
Created attachment 658243 [details] File: environ
Created attachment 658245 [details] File: limits
Created attachment 658246 [details] File: maps
Created attachment 658247 [details] File: open_fds
Created attachment 658248 [details] File: proc_pid_status
Created attachment 658249 [details] File: smolt_data
Created attachment 658250 [details] File: binary
After an update (#yum -y update) everytime I log in into my laptop the error message pop ups. HP EliteBook 8440p Intel Core i5 reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.9.4-200.fc18.x86_64 package: telepathy-mission-control-5.14.0-2.fc18 reason: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.