Hide Forgot
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/libexec/e-calendar-factory component: evolution-data-server crash_function: g_realloc executable: /usr/libexec/e-calendar-factory kernel: 2.6.35.10-74.fc14.i686 package: evolution-data-server-2.32.1-1.fc14 rating: 4 reason: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1296925887 uid: 500 How to reproduce ----- 1. opened evolution after adding a google calendar account 2. crash! 3.
Created attachment 477216 [details] File: backtrace
Thanks for a bug report. Based on the backtrace I guess it's either a memory corruption or your calendar contains some special recurring event, which is causing trouble to evolution. Is this reproducible consistently on your end, please? If it is, could you run e-calendar-factory under valgrind and reproduce the issue, please? You can run it like this, while no other e-calendar-factory is running: $ G_SLICE=always-malloc valgrind /usr/libexec/e-calendar-factory &>evo.txt and then run evolution from another console and reproduce the issue. File evo.txt may contain debugging information we are looking for. Please make sure you've installed evolution and evolution-data-server debug info packages before running the command and make sure there is not running any other e-calendar-factory (there can be only one at a time). Thanks in advance.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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