Evolution to exchange calender update bug

Bug #141231 reported by Ron Verhees
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-exchange
Fix Released
Medium
evolution-exchange (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Evolution Version: 2.12.0
Ubuntu Version: Gutsy Gibbon - Tribe 5

When creating an appointment in Evolution (using exchange plugin) it syncs back to the exchange server fine and is visible in Outlook Web Access (OWA).
However it does not synchronize to Palm Treo 750v smartphone running windows mobile version 6 properly.

The phone (running activesync between the exchange 2003 SP2 server) sees a new appointment is there and syncs it but it cannot be seen anywhere.
When opening the appointment via OWA, changing a something and saving it, it appears on the phone fine.

When creating an appointment directly through OWA or Microsoft Outlook everything works fine so this makes me believe Evolution writes something in the background that makes the phone ignore the appointment.
OWA when re-saving this message apparantly fixes this issue.

If anybody needs any more information feel free to contact me.

Revision history for this message
MattNewberry (matt-newberry) wrote :

Can confirm this in evolution 2.22 and Ubuntu Hardy 8.04 researching this points to public vs private event. Took this from http://bugzilla.gnome.org/show_bug.cgi?id=403903

----------------------------------------------------------------------------
I did some experimenting here, and it seems Outlook (web access (OWA) at least)
uses an empty CLASS: field if CLASS: is supposed to be PUBLIC.
and that this is what gets stored internally in exchange - But if I save such a
calendar event (created by OWA) by saving a message with a forwarded event in,
I get an explicit CLASS:PUBLIC - it is not clear to me whether this is done by
Evolution or if the PUBLIC word is added by Evolution - I found no way of
getting the event text out of OWA)

However, the following test I presume is good enough to verify that using an
empty CLASS: for PUBLIC is solving the problem(?) :

1) Create a public event in the exchange calendar using evolution
2) Sync your mobile device - the event does NOT show up.
3) Delete the event
4) create a forward mail with that event and save the mail to disk
5) edit the mail removing everything except the calendar event itself
6) Edit the class field - remove PUBLIC to leave it empty
7) Import the file as a calendar (.ics) file using the evolution import feature
8) sync your mobile device again - voila - the event shows up..

-----------------------------------------------------------------------------

Andreas Moog (ampelbein)
Changed in evolution-exchange:
status: New → Confirmed
Changed in evolution-exchange:
status: Unknown → New
Revision history for this message
dlstyley (deaston) wrote :

I have a very similar problem, except that the mobile device is an iPhone, which also uses OWA for sync.

http://ubuntuforums.org/showthread.php?t=921842

Is this the same as this bug report?

https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/115913

Changed in evolution-exchange (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Changed in evolution-exchange:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution-exchange - 2.30.2-0ubuntu1

---------------
evolution-exchange (2.30.2-0ubuntu1) maverick; urgency=low

  * New upstream release:
    - Appointments don't display in Windows Mobile 5 (LP: #141231, #115913)
    - Unnecessary check producing false critical warnings (Milan Crha)
    - Displays source of a message sent by RoadSync 5 (Milan Crha)
    - Updated translations
  * debian/control:
    - bump e-d-s build-dep to 2.30.2
 -- Didier Roche <email address hidden> Mon, 21 Jun 2010 15:31:05 +0200

Changed in evolution-exchange (Ubuntu):
status: Triaged → Fix Released
Changed in evolution-exchange:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.