Red Hat Bugzilla – Bug 1003668
[abrt] telepathy-mission-control-5.14.1-2.fc20: magazine_chain_pop_head: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:19:23 EDT
Version-Release number of selected component:
Thread no. 1 (10 frames)
#0 magazine_chain_pop_head at gslice.c:545
#1 thread_memory_magazine1_alloc at gslice.c:848
#2 g_slice_alloc at gslice.c:1007
#3 g_slist_prepend at gslist.c:267
#4 dbus_g_proxy_manager_register at dbus-gproxy.c:1015
#5 dbus_g_proxy_constructor at dbus-gproxy.c:1445
#6 g_object_new_with_custom_constructor at gobject.c:1665
#7 g_object_new_internal at gobject.c:1744
#8 g_object_new_valist at gobject.c:2002
#10 dbus_g_proxy_new at dbus-gproxy.c:1993
Potential duplicate: bug 883908
Created attachment 792910 [details]
Created attachment 792911 [details]
Created attachment 792912 [details]
Created attachment 792913 [details]
Created attachment 792914 [details]
Created attachment 792915 [details]
Created attachment 792916 [details]
Created attachment 792917 [details]
Created attachment 792918 [details]
Created attachment 792919 [details]
Created attachment 792920 [details]
Created attachment 792921 [details]
please retest with 0.15.0
still occurred with telepathy-mission-control-5.15.0-2.fc20
abrt decided it was a duplicate of this bug
I habe no idea.
reason: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Another user experienced a similar problem:
Booted the system.
reason: mission-control-5 killed by SIGSEGV
runlevel: N 5
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.