Red Hat Bugzilla – Bug 162398
evolution fails to access exchange server
Last modified: 2007-11-30 17:11:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2
Description of problem:
Whenever I start evolution it seems to hang. After a few minutes the evolution window comes up but is all grey.
If I keep waiting then it eventually comes up.
After some research it is a problem with talking to the exchange server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install FC 3, and use exchange
2. upgrade to FC 4, and run yum update
3. run evolution
4. wait and be unable to access exchange
5. have to go into work because you can no longer access your exchange email remotely
6. curse profusely at the upgrade and ask yourself why you did it
Actual Results: I spent a lot of time swearing... and evolution never would connect to exchange ..
Expected Results: it used to work, and connect to exchange, but now it doe snot
from strace it hangs in poll.. its like it suddenly cannot find the server. its there though
*** Bug 162399 has been marked as a duplicate of this bug. ***
fixed one problem, but it still takes 5 minutes to start up.
It seems that during the upgrade the https://exchange... got changed to
http://exchange... ( where ... is the exchange server)
it seems somehow the data got corrupted..
I'm more bother by why it is taking 5 minutes for evolution to start
I also had to remove some of the exchange directories and now things seem to be
Now, I occasionally just get an html page, that seems to be the exchange server
login page, only it does not show as the page it shows as html text. I'll see
if I can get a copy of what that looks like next time it happens.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
I no longer have access to that exchange server as I have changed jobs.
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.