Bug 1039782

Summary: [abrt] telepathy-mission-control-5.16.0-2.fc20: g_param_spec_get_default_value: Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alan Schmidt <bucky>
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: 20CC: bdpepple, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6bc5416ae1da9434597351640eb6f39dc9cfdf12
Whiteboard: abrt_hash:8e9f6e1e73654f5131513e72c9948bc93abd1493
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:27:08 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 Alan Schmidt 2013-12-10 01:30:17 UTC 
Description of problem:
All you have to do is boot up and login.

Version-Release number of selected component:
telepathy-mission-control-5.16.0-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/mission-control-5
crash_function: g_param_spec_get_default_value
executable:     /usr/libexec/mission-control-5
kernel:         3.11.10-300.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_param_spec_get_default_value at gparam.c:1560
 #1 g_object_new_internal at gobject.c:1777
 #2 g_object_new_valist at gobject.c:2002
 #4 _mcd_handler_map_new at mcd-handler-map.c:202
 #5 mcd_dispatcher_constructed at mcd-dispatcher.c:799
 #6 g_object_new_internal at gobject.c:1785
 #7 g_object_new_valist at gobject.c:2002
 #9 mcd_dispatcher_new at mcd-dispatcher.c:919
 #10 mcd_master_constructor at mcd-master.c:209
 #11 g_object_new_with_custom_constructor at gobject.c:1665
Comment 1 Alan Schmidt 2013-12-10 01:30:21 UTC 
Created attachment 834603 [details]
File: backtrace
Comment 2 Alan Schmidt 2013-12-10 01:30:23 UTC 
Created attachment 834604 [details]
File: cgroup
Comment 3 Alan Schmidt 2013-12-10 01:30:24 UTC 
Created attachment 834605 [details]
File: core_backtrace
Comment 4 Alan Schmidt 2013-12-10 01:30:25 UTC 
Created attachment 834606 [details]
File: dso_list
Comment 5 Alan Schmidt 2013-12-10 01:30:28 UTC 
Created attachment 834607 [details]
File: environ
Comment 6 Alan Schmidt 2013-12-10 01:30:29 UTC 
Created attachment 834608 [details]
File: exploitable
Comment 7 Alan Schmidt 2013-12-10 01:30:31 UTC 
Created attachment 834609 [details]
File: limits
Comment 8 Alan Schmidt 2013-12-10 01:30:32 UTC 
Created attachment 834610 [details]
File: maps
Comment 9 Alan Schmidt 2013-12-10 01:30:33 UTC 
Created attachment 834611 [details]
File: open_fds
Comment 10 Alan Schmidt 2013-12-10 01:30:36 UTC 
Created attachment 834612 [details]
File: proc_pid_status
Comment 11 Alan Schmidt 2013-12-10 01:30:38 UTC 
Created attachment 834613 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 09:57:11 UTC 
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'
of '20'.

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.
Comment 13 Fedora End Of Life 2015-06-29 13:27:08 UTC 
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.