Bug 800260
| Summary: | [abrt] evolution-3.3.90-1.fc17: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||||
| Component: | evolution-mapi | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 17 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:37f8f2a18f2d086a16b6d5751d0694272cd0e629 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-08-01 03:39:58 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
Mikhail
2012-03-06 07:33:44 UTC
Created attachment 567852 [details]
File: gconf_subtree
Created attachment 567853 [details]
File: build_ids
Created attachment 567854 [details]
File: dso_list
Created attachment 567855 [details]
File: maps
Created attachment 567856 [details]
File: backtrace
Thanks for a bug report. The attached backtrace is incomplete, unfortunately, it states there:
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
but what was kept above this message suggest some use-after-free in talloc code. I suppose this will be fixed with update on OpenChnage, which is planned for some time next week, then it'll land Fedora 17 with an update of evolution-mapi to 3.3.92. All that depends on the schedule of OpenChange update.
I'll keep this bug opened till it's done, for retesting.
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information. Bugs which were found to be similar to this bug: evolution: bug #579822, bug #597587, bug #600458, bug #600899, bug #617206, bug #635630, bug #648426 evolution-data-server: bug #630180, bug #682844, bug #687854 This comment is automatically generated. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. |