After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 272151 - Connector crashes after typing in password for Exchange
Connector crashes after typing in password for Exchange
Status: RESOLVED DUPLICATE of bug 268330
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.2
Other All
: Normal blocker
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
evolution[connector] evolution[folders]
Depends on:
Blocks:
 
 
Reported: 2005-02-03 01:42 UTC by Micah Nerren
Modified: 2005-02-09 06:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bug buddy trace (5.20 KB, text/plain)
2005-02-03 01:54 UTC, Micah Nerren
Details

Description Micah Nerren 2005-02-03 01:42:07 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Evolution-2.0.2 has been working fine for me ever since I installed Fedora
Core 3, with the exception of public folders on the Exchange server. I
attempted to add a Public Folder from Exchange by going to the Exchange
view, selecting the folder, right clicking and adding to Favorites. After
this, nothing showed up, so I closed Evolution and restarted it. Evolution
will now not let me view my Exchange mail box at all.

When I start Evolution, I click on the account for my exchange server, and
type in my password when prompted. I then am shown an Error box saying:

"The Application "evolution-exchange-storage" has quit unexpectedly."

I click on Close and am presented with the following error dialog:

"Error while scanning folders in "Exchange server exch01. Lost connection
to Evolution Exchange backend process."

Evolution 1.4.6 on my other computer still sees my exchange mail properly.

I have tried the following to back out anything I may have done wrong:

rpm -e evolution-connector evolution-devel evolution evolution-webcal
evolution-data-server-devel evolution-data-server --nodeps

Thus removing all the pieces of evolution and the connector that I could find.

rm -rf ~/.evolution
rm -rf /tmp/.evolution*
rm -rf ~/.gconf/apps/evolution*

Thus I assume I have totally removed the evolution configuration from my
system. I then reinstall evolution via yum:

yum install evolution-connector evolution-devel evolution evolution-webcal
evolution-data-server-devel evolution-data-server

I then restart evolution, reconfigure the connector to see my exchange
server, and it still crashes. I cannot figure out how to undo whatever I
did. Perhaps something was changed on my Exchange account on the server
which is causing this.

Steps to reproduce the problem:
1. Add public folder to favorites
2. Restart Exchange
3. 

Actual Results:
Evolution cannot access my exchange mail.

Expected Results:
Evolution should access my exchange mail.

How often does this happen? 
Always.

Additional Information:

I started Evolution from the command line with --debug set and this is the
contents of that file:
(evolution-2.0:8384): camel-WARNING **: Invalid root:
'/home/micah/.evolution/mail/local/Inbox.ibex.index'

(evolution-2.0:8384): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution-2.0:8384): camel-WARNING **: block size: 1024 (1024) OK

(evolution-2.0:8384): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution-2.0:8384): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution-2.0:8384): camel-WARNING **: flags: unSYNC

(evolution-2.0:8384): camel-WARNING **: Invalid root:
'/home/micah/.evolution/mail/local/Drafts.ibex.index'

(evolution-2.0:8384): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution-2.0:8384): camel-WARNING **: block size: 1024 (1024) OK

(evolution-2.0:8384): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution-2.0:8384): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution-2.0:8384): camel-WARNING **: flags: unSYNC

(evolution-2.0:8384): camel-WARNING **: Invalid root:
'/home/micah/.evolution/mail/local/Outbox.ibex.index'

(evolution-2.0:8384): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution-2.0:8384): camel-WARNING **: block size: 1024 (1024) OK

(evolution-2.0:8384): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution-2.0:8384): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution-2.0:8384): camel-WARNING **: flags: unSYNC

(evolution-2.0:8384): camel-WARNING **: Invalid root:
'/home/micah/.evolution/mail/local/Sent.ibex.index'

(evolution-2.0:8384): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution-2.0:8384): camel-WARNING **: block size: 1024 (1024) OK

(evolution-2.0:8384): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution-2.0:8384): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution-2.0:8384): camel-WARNING **: flags: unSYNC

(evolution-2.0:8384): evolution-mail-CRITICAL **: file
em-folder-tree-model.c: line 825 (em_folder_tree_model_remove_uri):
assertion `uri != NULL' failed

(evolution-2.0:8384): evolution-mail-WARNING **: Error occured while
existing dialogue active:
Lost connection to Evolution Exchange backend process
loading error file /usr/share/evolution/2.0/errors/e-system-errors.xml
loading error file /usr/share/evolution/2.0/errors/calendar-errors.xml
loading error file /usr/share/evolution/2.0/errors/addressbook-errors.xml
loading error file /usr/share/evolution/2.0/errors/filter-errors.xml
loading error file /usr/share/evolution/2.0/errors/mail-composer-errors.xml
loading error file /usr/share/evolution/2.0/errors/shell-errors.xml
loading error file /usr/share/evolution/2.0/errors/mail-errors.xml
Comment 1 Micah Nerren 2005-02-03 01:54:04 UTC
Created attachment 44737 [details]
bug buddy trace
Comment 2 Sarfraaz Ahmed 2005-02-08 06:41:25 UTC

*** This bug has been marked as a duplicate of 268330 ***
Comment 3 Micah Nerren 2005-02-08 22:05:13 UTC
I cannot see bug 268330. Is there a resolution to this bug? I get a
permission denied when I try to see the bug report.
Comment 4 Sushma Rai 2005-02-09 05:58:50 UTC
Try 2.0.3, which has fix for this problem.
Comment 5 Sarfraaz Ahmed 2005-02-09 06:43:54 UTC
Provided permissions for 68330 to be viewed by all.