Version-Release number of selected component: telepathy-mission-control-5.16.0-2.fc21 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.13.0-0.rc0.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 42 Truncated backtrace: 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 g_object_notify_queue_add at gobject.c:306 #5 object_set_property at gobject.c:1381 #6 g_object_new_internal at gobject.c:1755 #7 g_object_new_valist at gobject.c:1978 #9 mcd_dispatcher_new at mcd-dispatcher.c:919 #10 mcd_master_constructor at mcd-master.c:209 Potential duplicate: bug 883908
Created attachment 823971 [details] File: backtrace
Created attachment 823972 [details] File: cgroup
Created attachment 823973 [details] File: core_backtrace
Created attachment 823974 [details] File: dso_list
Created attachment 823975 [details] File: environ
Created attachment 823976 [details] File: exploitable
Created attachment 823977 [details] File: limits
Created attachment 823978 [details] File: maps
Created attachment 823979 [details] File: open_fds
Created attachment 823980 [details] File: proc_pid_status
Created attachment 823981 [details] File: var_log_messages
Another user experienced a similar problem: In the background, I did not trigger directly. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.13.0-0.rc4.git4.1.fc21.x86_64 package: telepathy-mission-control-5.16.0-2.fc21 reason: mission-control-5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Another user experienced a similar problem: Background failure. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.13.0-0.rc3.git3.1.fc21.x86_64 package: telepathy-mission-control-5.16.0-2.fc21 reason: mission-control-5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
I've also experienced it on F20, same Telepathy version. I've filed it upstream. It looks like a memory corruption to me, so it would be useful to run mission-control in Valgrind. Are you able to reproduce the bug? I don't think I am.
Another user experienced a similar problem: Happened during boot. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: magazine_chain_pop_head executable: /usr/libexec/mission-control-5 kernel: 3.13.0-0.rc7.git1.1.fc21.x86_64 package: telepathy-mission-control-5.16.0-2.fc21 reason: mission-control-5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
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.