Bug 649527 - Evolution cannot open calendar on Exchange
Summary: Evolution cannot open calendar on Exchange
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-exchange
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 21:46 UTC by Bojan Smojver
Modified: 2010-11-10 09:01 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-10 07:48:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bojan Smojver 2010-11-03 21:46:41 UTC
Description of problem:
As of F-14, Evo cannot open calendar on Exchange (when used with evolution-exchange).

Version-Release number of selected component (if applicable):
2.32.0-1.fc14.i686

How reproducible:
Always.

Steps to Reproduce:
1. Set up a new Exchange account.
2. Access your e-mail.
3. Attempt to open calendar.
  
Actual results:
Error loading calendar
Cannot open calendar: Calendar does not exist

Expected results:
Worked in F-13.

Additional info:

Comment 1 Bojan Smojver 2010-11-04 01:30:16 UTC
Just a sidenote, it seems that the settings picked during setup of an account are not carried forward. This includes things like check all folders for mail, secure/plaintext password etc.

Also, setting Exchange password mode to plaintest seems to crash e-cal and e-add more. Just FYI. I submitted a whole bunch of backtraces to this effect.

Comment 2 Bojan Smojver 2010-11-04 01:45:06 UTC
Another note: what seems at random, when I access contact/GAL/calendar, Evo will ask for password. I supply it and ask for it to be save (although there is on in the keyring already). Still, Evo keeps asking for it. Eventually, I press cancel and get cannot open calendar due to authentication problems. Well, yeah... :-)

Comment 3 Bojan Smojver 2010-11-04 03:25:08 UTC
General comment: I did try using MAPI, but that was just way too slow for the amount of e-mail I have. So, I'm stuck with evo-exchange for now.

Comment 4 Bojan Smojver 2010-11-09 22:41:50 UTC
Ping...

Can anyone confirm this bug? The 2.32.1 release date is coming and would be really good if this issue can be dealt with. This is a regression from F-13.

Comment 5 Milan Crha 2010-11-10 07:07:49 UTC
Thanks for a bug report, but this works for me, fresh install, newly configured exchange account. Could this be related to bug #649198? But it may crash the application. Just in case, before you run evolution, make sure the 
~/.cache/evolution/calendar exists.

Comment 6 Bojan Smojver 2010-11-10 07:38:33 UTC
(In reply to comment #5)
> Thanks for a bug report, but this works for me, fresh install, newly configured
> exchange account. Could this be related to bug #649198? But it may crash the
> application. Just in case, before you run evolution, make sure the 
> ~/.cache/evolution/calendar exists.

Not sure, to be honest.

That directory does exist and it appears to have broken links in there. I'm going to remove ~/.cache/evolution ~/.local/share/evolution and run gconftool-2 --recursive-unset /apps/evolution. Then I'm going to set everything up again. Will let you know what happens.

PS. I did set everything up a few times already.

Comment 7 Bojan Smojver 2010-11-10 07:48:17 UTC
(In reply to comment #6)
 
> Not sure, to be honest.

Yeah, you are right there. Just clicked on calendar after setup and e-calendar-factory promptly crashed, with nothing in .cache/evolution/calendar. Workaround from https://bugzilla.gnome.org/show_bug.cgi?id=632669#c23 works.

Closing and thank you.

Comment 8 Milan Crha 2010-11-10 08:35:08 UTC
Thanks for a quick update. It might be interesting to know what actually was happening with the previous setup, though if the link was broken, then it probably was it.

Comment 9 Bojan Smojver 2010-11-10 09:01:29 UTC
There were two sets of links there. One set with Basic, the other with NTLM, both pointing nowhere (I guess .evolution dir is no more). I didn't clean up .cache/evolution before last setup attempt.

I also noticed thar setting auth to secure password (in receiving options) renders calendar/tasks unusable. Also, setting secure password in gal settings renders contacts unusable, while gal works. Setting plaintext there makes contacts works, but gal then fails. The only thing that works for both contacts/gal is secure or plaintext.

Not sure if this has to do with particular Exchange server configuration (it is 2003). Anyway, I cannot change that bit.


Note You need to log in before you can comment on or make changes to this bug.