Red Hat Bugzilla – Bug 160451
Evolution crashes on view change or preference update
Last modified: 2007-11-30 17:11:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Description of problem:
When evolution is running, if I select the Settings menu and then close the settings dialog evolution crashes with a segmentation fault.
The same happens after having changed a calendar or addressbook view and then reopening Evolution.
I ran a gdb with the debug packages installed. See attachment
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch evolution
2. Select settings from Tools menu
3. Change a setting in any tab
4. click on Close button of settings dialog
5. Evolution crashes
Actual Results: Evolution crashes with segementation fault
Expected Results: window should close and evolution should continue to run as normal
This bug only started to appear around May 27th 2005. Before evolution was working normally. I have been regularly updating FC3 components with yum.
I have tried with a new gconfd tree for evolution and a new data store and the problem still occurs.
Created attachment 115464 [details]
Backtrace results from gdb
Created attachment 115465 [details]
Backtrace results from bug buddy
Found this bug in Gnome BugZilla that looks exactly like the problem I am having:
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report. If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Closing as INSUFFICIENT_DATA.