Bad evolution/sunbird interaction with google calendar stores & zimbra-created events

RESOLVED INCOMPLETE

Status

Calendar
Provider: CalDAV
RESOLVED INCOMPLETE
9 years ago
6 years ago

People

(Reporter: Olin Shivers, Unassigned)

Tracking

Sunbird 0.9
x86
Linux

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060309 Ubuntu/9.04 (jaunty) Firefox/3.0.11
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.18pre) Gecko/20090408 Ubuntu/9.04 (jaunty) Sunbird/0.9

Short summary: I can't use evolution or sunbird to move zimbra-created events
from a zimbra CalDAV store to a google calendar.

For the following scenario, assume that I have two calendar stores, which
I am remotely accessing from two clients:
- a zimbra calendar and a google calendar
- both accessed via CalDAV from evolution and sunbird.
(Plus I can access the zimbra store using zimbra's web client.)

Let's assume that we can successfully create, modify and delete events
on both stores from both evolution & sunbird.

Now do the folloing:

1. Create an appt with evolution on the google cal.
   Create an appt with sunbird on the google cal.
   Note: we clearly have write access to the google calendar 
   from these clients.

2. Create an appt with zimbra's web client on a zimbra calendar store.
   Open the appt in evolution; change its calendar to the google
       calendar & save.
   What will happen: evolution will pop up an error window saying
       "Authentication failed"
   (If, instead, you use the "move appt" or "copy appt" operation,
   it just silently fails.)

3. Now create another appt in the zimbra store, but this time,
   create it using evolution, not the zimbra web client.
   As before, open the appt in evolution; change its calendar to the google
       calendar & save.
   What will happen: it works.

4. Now try all of the above, using Mozilla Sunbird instead of evolution.
   It comes out exactly the same (except that Sunbird fails less gracefully:
   It displays a pop-up saying "An error occurred when writing to the calendar
   <the google calendar>!" with "MODIFICATION_FAILED" as the error "number;"
   the event is then lost -- it no longer even appears on the zimbra calendar
   (oops).

Comments:

1. The fact that this fails in both evolution and sunbird makes me suspicious
of google's CalDAV service.

2. The fact that it fails only with events created using zimbra's web client
makes me suspicious of that client. I know, for example, that zimbra's web
client includes a ORGANIZER field in simple non-meeting appointment records, 
while evolution does not.
    -Olin


Reproducible: Always

Steps to Reproduce:
See above.

Comment 1

9 years ago
Please report issues with Evolution somewhere else. This Bugzilla installation tracks only calendar issues for Sunbird/Lightning product.

Please check Tools > Error Console for some extended error information.

Please retest with a recent Sunbird 1.0pre nightly test build. Several CalDAV and Zimbra related issues (e.g. Bug 464133) have been fixed since the 0.9 release.
Version: unspecified → Sunbird 0.9
(Reporter)

Comment 2

9 years ago
> Please report issues with Evolution somewhere else. This Bugzilla
> installation tracks only calendar issues for Sunbird/Lightning product.

The evolution information is of interest because it helps assign
"blame" in the client/server interaction -- it's useful to know
if a *different* client triggers the *same* bad behavior.

> Please retest with a recent Sunbird 1.0pre nightly test build. Several
> CalDAV and Zimbra related issues (e.g. Bug 464133) have been fixed since the
> 0.9 release.

I tried things again with tonight's "nightly build" Sunbird. Here's the build
info from the "About Calendar" popup:

    Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.1pre) 
    Gecko/20090701 Calendar/1.0pre

It still loses.

> Please check Tools > Error Console for some extended error information.

I append the logged messages from the error console. These two
messages are logged at the same time: when I click "Save and Close"
after changing the test event's calendar from the Zimbra CalDAV store
to the Google calender CalDAV store. Note that the file:///tmp/sunbird/...
urls are due to the fact that I unpacked the "nightly build" tarball
in /tmp/.
    -Olin

Warning: There has been an error reading data for calendar: goog-fam.
However, this error is believed to be minor, so the program will attempt to
continue. Error code: DAV_PUT_ERROR. Description: There was an error storing
the item on the server.

Error: An error occurred when writing to the calendar goog-fam! Error code: MODIFICATION_FAILED. Description: 
Source File: file:///tmp/sunbird/modules/calUtils.jsm -> file:///tmp/sunbird/calendar-js/calCalendarManager.js
Line: 976
Please enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor (Options > Advanced > General > Config Editor) and check your error console for messages.

Comment 4

6 years ago
Reporter please include the information requested in comment #3. Moreover, please attach ics files of the involved events.
Otherwise this will be closed soon.
Whiteboard: [closeSoon]

Comment 5

6 years ago
Reporter please reopen, if you can provide the logs requested in comment #3.

Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeSoon]
You need to log in before you can comment on or make changes to this bug.