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 631439 - Calendar Items creating in Evolution don't sync to mobile devices.
Calendar Items creating in Evolution don't sync to mobile devices.
Status: RESOLVED DUPLICATE of bug 403903
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-10-05 14:43 UTC by Harald van Bree
Modified: 2010-10-06 04:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Harald van Bree 2010-10-05 14:43:00 UTC
Hi,

Since quit a while now I am unable to create a Calendar Item that will Sync to my Mobile device.

What I do is the following:

Create a New Appointment.
Within I select my Exchange Calendar as Calendar Resource.
I fill out all the fields. (summery, Location and pick a time slot )
Then I save this item and it shows up in Evolution nicely. It even shows up in Outlook web access. But it never get synced to my mobile device.

At this time I'm using Android 2.2 but have used Windows mobile 6 and 6.5 with the same results.


Now the good part.
When I create a new appointment from within Outlook web access I MUST include myself as an attendee. The Invitation is then placed in my Mailbox so I can accept the appointment. The Item created from within evolution is NOT including me as an Attendee.

So the next step I took was creating a Meeting. The outcome of this test is the same as creating a Appointment.

Is there any change this can be fixed.
Comment 1 Akhil Laddha 2010-10-06 04:03:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 403903 ***