| Summary: | [abrt] evolution-3.0.3-1.fc15: check_derivation_I: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yann Droneaud <yann> | ||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | lucilanga, mbarnes, mcrha | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:bcc2141225acf05d5b74f5304e9bbe1b79de2241 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-08-07 17:06:07 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
Yann Droneaud
2011-11-09 16:27:47 UTC
Created attachment 532606 [details]
File: xsession_errors
Created attachment 532607 [details]
File: maps
Created attachment 532608 [details]
File: backtrace
Thanks for a bug report. This seems like some kind of memory corruption, on the first look. Are you able to reproduce this reliably, please? If yes, could you run evolution under valgrind, to see whether it'll find anything useful, please? Just make sure you've installed debug info packages for evolution-data-server and for evolution, then invoke this command: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt and wait whether will evolution crash or not. The new log.txt file may contain some information. (In reply to comment #4) > Thanks for a bug report. This seems like some kind of memory corruption, on the > first look. Are you able to reproduce this reliably, please? Sadly not : I'm not able to reproduce the crash. But the bad news for me: some of my email are scrambled : the message list doesn't match the message content: eg the message subject in the list is not the one I have in the message view (especially the oldest one, those on top of the list). I'm trying to get the thing synchronized back, but I have failed to. It's possible that the local summary file have been corrupted due to the crash. What is the folder you have the issue with, please? If it's one of those under On This Computer, then its folder summary is saved in ~/.local/share/evolution/mail/local/folders.db file, thus try to close evolution and move that file away. Then run evolution and the file will be recreated from scratch. You may loose some locally stored information, like labels or follow-up tags, if you use them, but apart of that nothing will be lost, definitely no mail message. Note that I suggested to move the file away, not delete it, because if something will go wrong then you should be able to place it back in order to get to the current state. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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 |