Bug 853039
Summary: | [abrt] evolution-3.2.3-3.fc16: __libc_message: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dev Adeshara <dev.adeshara23> | ||||||||||||||||
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||
Priority: | unspecified | ||||||||||||||||||
Version: | 16 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | i686 | ||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||
Whiteboard: | abrt_hash:70a296b62c0d8ea6022c257f900ec90b1d519822 | ||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2013-02-13 17:45:51 UTC | Type: | --- | ||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
Embargoed: | |||||||||||||||||||
Attachments: |
|
Description
Dev Adeshara
2012-08-30 10:51:07 UTC
Created attachment 608144 [details]
File: event_log
Created attachment 608145 [details]
File: backtrace
Created attachment 608146 [details]
File: gconf_subtree
Created attachment 608147 [details]
File: xsession_errors
Created attachment 608148 [details]
File: maps
Created attachment 608149 [details]
File: dso_list
Created attachment 608150 [details]
File: build_ids
Thanks for a bug report. The bactrace shows detected memory issue by glibc, inside new memory chunk allocation, which usually means that the memory corruption happened some time before this call. Apart of missing debug information for evolution-data-server, do you have any steps how to reproduce this, please? It may help to identify the issue, though it's true it's usually hard to reproduce memory corruption bugs. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |