Bug 50832

Summary:	Attempting to open Evolution settings dialogs causes crashes
Product:	Ports & Packages	Reporter:	Christopher Nehren <apeiron>
Component:	Individual Port(s)	Assignee:	freebsd-gnome (Nobody) <gnome>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Latest
Hardware:	Any
OS:	Any

Description Christopher Nehren 2003-04-11 18:40:13 UTC

Whenever I try to go to various tabs in the Evolution Settings dialog, the relevant component crashes. Sometimes it's the "Summary" component, other times it's the "Mail" component. I've seen no discernible pattern for these crashes, except that they don't occur without an existing evolution/ directory. I could simply remove my evolution/ directory, but I have archived emails which I'd rather not remove.

Fix: 

Removing the Evolution directory and starting over does seem to solve the problem, but I don't think users would want to just dispose of their emails so their client will work again.
How-To-Repeat: Upgrade to Evolution 1.2.4 from a previous version, and try to open the Settings menu.

Comment 1 Adam Weinberger freebsd_committer

2003-04-11 23:59:54 UTC

Responsible Changed
From-To: freebsd-ports-bugs->gnome

Over to maintainers.

Comment 2 Joe Marcus Clarke freebsd_committer

2003-04-12 20:15:18 UTC

State Changed
From-To: open->feedback

You didn't give us much to go on.  When reporting crashes, you should 
come with core dump backtraces, error messages, etc. 

With 5.x, it's best you rebuild all of evolution's requirements to make sure 
they've all been compiled under the same ABI.  This is best done with 
sysutils/portupgrade and the command portupgrade -Rf evolution.  However, 
if you still find it's crashing, you can delete the preferences files 
under ~/evolution without losing any mail.  Simply save off the  
~/evolution/local directory, delete ~/evolution, then restore the local 
directory when you have everything set back up. 

Let us know if the recursvie rebuild helps.

Comment 3 Joe Marcus Clarke freebsd_committer

2003-05-02 07:10:12 UTC

State Changed
From-To: feedback->closed

Timeout from submitter, and I am unable to reproduce this locally.