Bug 841429
| Summary: | [abrt] evolution-3.2.3-3.fc16: g_cancellable_cancel: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nelufar <nelufar_up> | ||||||||||
| 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: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:1266b9adf1555964b86cfa53529efc399d81ed84 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-02-13 17:43:06 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
nelufar
2012-07-19 01:06:26 UTC
Created attachment 599023 [details]
File: dso_list
Created attachment 599024 [details]
File: build_ids
Created attachment 599025 [details]
File: maps
Created attachment 599026 [details]
File: backtrace
Thanks for a bug report. I see from the backtrace that this happened when you were removing mail account from Preferences. I search upstream bugzilla, but I didn't find this crash there. I would like to ask whether you are able to reproduce this on current stable, which is 3.4.3 under Fedora 17. I did remove accounts in that version recently, and it didn't crash here, thus I guess this is already fixed in Fedora 17, or this requires specific steps to reproduce. I don't have Fedora 17, so I cannot say about that. But after a reboot I was able to start evolution and the account was also not deleted. Yup, it seems like evolutiuon crashed before the account was deleted. Maybe if you could find steps to reproduce, then I can test in Fedora 17 (or try a LiveCD, in case you do not plan to update in a near future). 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. |