| Summary: | [abrt] evolution-3.0.1-1.fc15: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Luken <lukenrd> | ||||||||||
| 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, wget.null | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:49f0fd3ecd24a43a9f6f86e0d06999bec7536fc1 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-08-07 17:04:08 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
Robert Luken
2011-05-19 21:17:11 UTC
Created attachment 499950 [details]
File: maps
Created attachment 499951 [details]
File: backtrace
Thanks for a bug report. I see this happened when gkt+ tried to draw the GtkTreeView, most likely the folder tree on the left. One possibility is that the folder name used for it is some already freed memory, or a garbage pointer, but that's pretty unlikely. Other threads in the backtrace looks irrelevant, rather in idle. You said above that it's a random crash, so I suppose you cannot reproduce it. But just in case, to avoid something "simple", could you run evolution under valgrind to see whether there isn't anything wrong with memory, and only by luck it doesn't crash, please? You can run it like this: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt and let it load the interface with all folders, then maybe read a mail or two and then just close evolution and attach the resulting log.txt here, I'll see whether it'll give us any hint on the issue. Only note that evolution will be significantly slower due to all memory checking. Thanks in advance. same, reinstall evolution and it'll crash with a error 6 in libical.so.0.46.0 abrt.log att, also memory log. Created attachment 524724 [details]
memory map
Created attachment 524725 [details]
abrt-log
Thanks for the update. I would think of an issue in libical, but because your .xsession-errors is showing this:
> :(evolution-settings:2181): evolution-shell-CRITICAL **:
> e_shell_get_express_mode: assertion `E_IS_SHELL (shell)' failed
and many other similar lines, then I do not think it's a case here. We might try to find why this is happening for you. After you reinstalled evolution, did the uninstall remove all your previously configured accounts, thus when you run evolution you are asked to fill a new one? Though even then you shouldn't see errors with EShell instances, because it's an object which is created as one of the first when application starts.
I'm also not sure whether it's the same issue as the initial one, because this is crashing in a different function.
I'm also not sure, that case was closer then other. Yes, I can reproduce the crash everytime. I deleted all accounts, files under ~/.cache/evolution*, and remove evolution. First start will crash too. But I can create accounts with evolution-settings. I see the same error always, so I started evolution with strace and the error occurs after it'll load the timezone from Africa (could also be the last in the list). At the evening I'm a my laptop so I can send you the trace. thanks, Alex The libical issue should be fixed with an update on it, please open a new bug report against libical. I'm not sure when the update will be done on the libical side, but the maintainer of the package in Fedora may try to backport the change [1] before 0.47 will be released officially. [1] http://sourceforge.net/mailarchive/forum.php?thread_name=201103081755.02449.winter%40kde.org&forum_name=freeassociation-devel 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 |