Ubuntu

Calendar Refresh Issue When Connecting to Exchange 2003 through OWA

Reported by Neal Gamradt on 2012-03-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Undecided
Unassigned

Bug Description

I am running Ubuntu 12.04 with Evolution 3.2.3. I have to connect to our work Exchange 2003 system for my e-mail and calendar. This used to work well in older versions of Ubuntu (10.04 through 11.04). However, ever since 11.10 (Evolution 3.2.1) the calendar portion hasn't worked well at all.

A few odd things to note, in Synaptic all of the Evolution packages are version 3.2.3 except for the evolution-exchange, that package is only at version 3.2.1-2ubuntu1. I am wondering if this is the correct package or not?

The behavior I am noticing with the calendar is that it almost works. When you first log into Evolution, the calendar loads without issue. However as soon as you leave the calendar and come back, the data is "stale", you can see the data from the last day you were viewing, but if you click on any other days, all the meeting notices are gone.

I have found that if I uncheck the exchange calendar and check it again, then all the data is current again. But it will only stay "fresh" for a short amount of time. Then if you want to see updates, the "Refresh" link is useless, you have to uncheck and check the Exchange calendar again and the data is fresh again.

I have tried endless combinations of setting, from disabling the local caching to making this calendar the only (and default) calendar. So far the bug works exactly the same regardless of my settings.

Meeting notices don't work either, but I am guessing that has something to do with this connection going stale.

Please let me know if you need more details on this. In Ubuntu 11.10 this behavior was completely random (as I reported in the following bug at that time: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/897300

Beyond this issue Evolution is working very well for my e-mail needs, I am hopeful that this issue can be resolved.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers