Bug 1030480

Summary: [abrt] telepathy-mission-control-5.16.0-2.fc21: magazine_chain_pop_head: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: telepathy-mission-controlAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: awilliam, bdpepple, nalimilan, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a496dbd4f20e827631ffb4c3ccf4ebc30d396fcd
Whiteboard: abrt_hash:48e643e28661c202ccc43629684292966dd73a24
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:35:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Tom London 2013-11-14 14:20:45 UTC 
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
Comment 1 Tom London 2013-11-14 14:20:52 UTC 
Created attachment 823971 [details]
File: backtrace
Comment 2 Tom London 2013-11-14 14:20:54 UTC 
Created attachment 823972 [details]
File: cgroup
Comment 3 Tom London 2013-11-14 14:20:58 UTC 
Created attachment 823973 [details]
File: core_backtrace
Comment 4 Tom London 2013-11-14 14:21:00 UTC 
Created attachment 823974 [details]
File: dso_list
Comment 5 Tom London 2013-11-14 14:21:03 UTC 
Created attachment 823975 [details]
File: environ
Comment 6 Tom London 2013-11-14 14:21:06 UTC 
Created attachment 823976 [details]
File: exploitable
Comment 7 Tom London 2013-11-14 14:21:09 UTC 
Created attachment 823977 [details]
File: limits
Comment 8 Tom London 2013-11-14 14:21:13 UTC 
Created attachment 823978 [details]
File: maps
Comment 9 Tom London 2013-11-14 14:21:16 UTC 
Created attachment 823979 [details]
File: open_fds
Comment 10 Tom London 2013-11-14 14:21:20 UTC 
Created attachment 823980 [details]
File: proc_pid_status
Comment 11 Tom London 2013-11-14 14:21:23 UTC 
Created attachment 823981 [details]
File: var_log_messages
Comment 12 Adam Williamson 2013-12-20 05:11:23 UTC 
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
Comment 13 Adam Williamson 2013-12-20 05:18:10 UTC 
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
Comment 14 Milan Bouchet-Valat 2013-12-25 10:11:45 UTC 
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.
Comment 15 Adam Williamson 2014-01-08 20:31:49 UTC 
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
Comment 16 Jaroslav Reznik 2015-03-03 15:12:33 UTC 
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
Comment 17 Fedora End Of Life 2016-07-19 10:35:38 UTC 
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.