Bug 235525

Summary: How to completely hose your Evolution + Exchange configuration
Product: [Fedora] Fedora Reporter: Jonathan Kamens <jik>
Component: evolution-connectorAssignee: Matthew Barnes <mbarnes>
Status: CLOSED RAWHIDE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-03 00:46:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2007-04-06 18:21:10 UTC 
Here's how to completely hose your Evolution + Exchange configuration, such that
all you can do to recover from it (at least, all I could find to do) is to start
blowing away ~/.evolution, ~/.gconf/apps/evolution, the evolution lines in
~/.gconfd/saved-state, etc., until things are cleaned up enough that you can
reconfigure everything from scratch.

1. View an Exchange folder.
2. In the search bar, change "Current Folder" to "Current Account".

You'll immediately get a dialog telling you that the connection to the exchange
connector process was lost.  Try to click OK; if you're lucky, it may even let
you.  Then it'll tell you again, and again.  Try killing and restarting
Evolution; nope, you're back in the same state.  Try starting in off-line mode.
 *Maybe* that will work, except I'm not sure because at some point during all
this I inadvertently made things even worse by changing "Current Account" to
"All Accounts", which completely and utterly hosed everything and brought my
machine to such a level of hosage that I had to hit the reset button.

jik2:~!1068$ rpm -q evolution evolution-connector evolution-data-server 
evolution-2.10.0-10.fc7
evolution-connector-2.10.0-1.fc7
evolution-data-server-1.10.0-6.fc7
Comment 1 Jonathan Kamens 2007-04-06 18:32:54 UTC 
It looks like killing all the evolution processes with evolution
--force-shutdown and then removing all the cmeta files in ~/.evolution is
sufficient to solve the problem.
Comment 2 Matthew Barnes 2007-10-02 18:20:22 UTC 
Is this problem still present in Fedora 8 Test 2 or later?
Comment 3 Jonathan Kamens 2007-10-03 00:46:32 UTC 
I can't reproduce this in the current Rawhide RPMs.