|Summary:||[abrt] telepathy-mission-control: g_malloc(): mission-control-5 killed by SIGTRAP|
|Product:||[Fedora] Fedora||Reporter:||piio <bugzilla>|
|Component:||telepathy-mission-control||Assignee:||Peter Robinson <pbrobinson>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2017-08-08 12:09:14 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description piio 2015-08-18 13:32:39 UTC
Version-Release number of selected component: telepathy-mission-control-5.16.3-3.fc24 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/mission-control-5 crash_function: g_malloc executable: /usr/libexec/mission-control-5 global_pid: 3428 kernel: 4.2.0-0.rc7.git0.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000
Comment 13 piio 2016-02-24 07:29:02 UTC
The problem still happens: msg = 0x7fe6340008c0 "gmem.c:100: failed to allocate 18446744073709551581 bytes" msg_alloc = 0x7fe6340008c0 "gmem.c:100: failed to allocate 18446744073709551581 bytes"
Comment 14 Jan Kurik 2016-02-24 13:38:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 15 Fedora End Of Life 2017-07-25 19:10:39 UTC
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 16 Fedora End Of Life 2017-08-08 12:09:14 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.