Hide Forgot
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: evolution component: evolution executable: /usr/bin/evolution kernel: 2.6.37vpv2-fatfix package: evolution-2.32.2-1.fc14 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) How to reproduce: 1. Tried to start the new Evolution version in updates-testing time: 1297238611 uid: 500
Created attachment 477763 [details] File: backtrace
Running "for i in /etc/gconf/schemas/*evolution* ; do gconftool-2 --install-schema-file $i ; done" taken from bug 597993 fixes the problem. Maybe this was caused by having Evolution running while applying the updates? After the updates had been installed, I ran "evolution --force-shutdown" and then tried to start it again.
Thanks for a bug report. To be honest I do not understand the crash much. It has an issue when looking for a schema definition of "/apps/evolution/mail/display/address_compress" but that key is included since 2006 and the .spec file has installation of this schema file in post-install steps, so they might be there. Did you have installed previous version of evolution, and/or using it without nay issue? I'm asking, because I'm not aware of anything what might this update change in this area.
(In reply to comment #3) > Did you have installed previous version of evolution, and/or using it without > nay issue? Yes. I had the previous Fedora package installed and used it daily. Something may have gone wrong with this particular update. I installed this update on another system and it worked fine there.
OK, I cannot think of anything what that could be. Maybe some kind of coincidence? I do not think the downgrade and upgrade of evolution may reproduce the issue, so what should I do with this bug report? And because you said it's working on another machine, so this can be also machine-dependant, then what about the update comment you added, would you comment there too, please?
I reported this bug with ABRT before googling for the workaround. Of course, it would be nice to know what's causing this, since there is at least one other report of the same problem. This is probably really hard to reproduce and debug, though. If you want to close the bug, it's fine with me. I'll comment on the update.
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