1377212 - Lightning dos not synchronize to davical server

Status: UNCONFIRMED

(Calendar :: Provider: CalDAV, defect)

Description

[Walter W.]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce:

Install thunderbird for Windows for a new windows user (52.2.1 (32-Bit)).
Mails are working.
Go to calendar tab, create a new calendar of type caldav (pointing to a linux davical server) with default settings, which are working correctly in the same network on different windows computers (Windows 10).
When asked for the davical username and password, input is accepted.
Press ready and wait.




Actual results:

Still after waiting 20 minutes, no data is shown in the calendar area.
Watching the files in the directory c:\Users\XXXX\AppData\Roaming\Thunderbird\Profiles\640be77n.default\calendar-data\ , the size of these files keep constant.


Expected results:

Lightning should synchronize with the caldav server and show the data of the davical server.

On other Thunderbird - Windows workstations in the same network the davical server is synchronized correctly.

Comment 1

[Walter W.]

Maybe I forgot to mention, that there are no error messages, no yellow triangles. Just no calendar events are shown.

Comment 2

[Walter W.]

We made new tests. On workstations with working connection to Davical we unsubscribed the calendar "Davical". The calendar vanished.
Then we tried to subscribe again to the same server. Now there is no synchronization as in the newly installed workstations.

I saved the profile directory before this test. 
After the change and no working synchronization I stopped Thunderbird, copied the previous prefs.js and the directory "calendar-data" and started thunderbird again. Now the synchronization is working again as before.
I did not find anything much difference in both prefs.js (working and not working). So I think it has something to do with the sqlite-database, maybe the calendar-properties in cal_metadata?

Comment 3

[Walter W.]

As we found no solution, we changed from Davical to Baikal (http://sabre.io/baikal/).
We exported the calendar data at one of our working stations and imported to the new Baikal-based calendar.

Now all is working.