#550195 evolution: Contacts on WebDAV don't work

Package:
evolution
Source:
evolution
Description:
groupware suite with mail client and organizer
Submitter:
Xavier Bestel
Date:
2017-09-24 13:21:03 UTC
Severity:
normal
#550195#5
Date:
2009-10-08 10:41:40 UTC
From:
To:
Hi,

I have setup a custom web server (apache2 + mod_dav) to store my contacts. It works quite well with Evo 2.26
from Ubuntu, but the same setup with Evo 2.28 from Debian/sid doesn't (can't read anything, can't create new
contact, and an error message just states that something went wrong (in French)).

Running evolution-data-server in its own shell gives that strange message:

(process:28570): libebookbackendgoogle-WARNING **: PROPFIND on webdav failed with http status 4

Which is very strange, because my contacts aren't declared as Google but as WebDAV.

Thanks,
	Xav

#550195#10
Date:
2009-10-30 09:41:56 UTC
From:
To:
FWIW, I tested with Evo 2.26 on Fedora 11 and Evo 2.28 on Ubuntu, and it
works very well.
It looks like a bug in Debian's packages.

	Xav

#550195#15
Date:
2009-10-30 10:16:17 UTC
From:
To:
Does anyone has any hint on how to debug that please ?
I tried adding CALDAV_DEBUG=1 (or CALDAV_DEBUG=all) when running
evolution and evolution-data-server, but it didn't help.

The only debug info I have is this:

(evolution:25787): calendar-gui-WARNING **: e-cal-model.c:1874: Unable to get query, Le moteur est occupé

(evolution:25787): calendar-gui-WARNING **: Unable to load the calendar Erreur inconnue

In English, that means "the engine is busy", then "Unknown error".
Not very helpful.

Thanks,
	Xav

#550195#20
Date:
2009-10-30 10:21:47 UTC
From:
To:
Hi,

Forget that message, it was for bug #505248.
But anyway I'd like to know how I can help debug that.

Thanks,
	Xav

#550195#25
Date:
2009-10-31 11:11:43 UTC
From:
To:
So the same happens on other distros?

No idea, sorry. Try looking on bugzilla.gnome.org, maybe

#550195#30
Date:
2009-10-31 11:36:18 UTC
From:
To:
Le samedi 31 octobre 2009 à 12:11 +0100, Yves-Alexis Perez a écrit :

No, only on Debian. It's just that contacts are on WebDAV, and thoses
variables are thoses I used when debugging CalDAV troubles.

The problem is that it only happens on my Debian machine.

	Xav

#550195#35
Date:
2009-12-30 18:33:04 UTC
From:
To:
it.

        Xav

#550195#40
Date:
2010-09-21 11:32:19 UTC
From:
To:
Hi,

I previously used WebDAV contacts in the past, but they don't seem to
work at all for me now.  I have tested this with a new install of
Squeeze into a 32-bit VM, and with my main laptop running 64-bit Sid.

I have tried with, and without proxies operating, as suggested in an
earlier message to this bug report.

This is excessively vexatious for me as I just added CardDAV support to
my CalDAV server and Evolution was *working* with this in the past
(dammit :-)

I have looked for traffic leaving Evolution with Wireshark, and as far
as I can see it actually does not get as far as starting an HTTP
connection, just sitting there with a spinner saying "Loading
Addressbook Summary..." in the status bar while it says "Searching for
the Contacts..." in the main panel.

If you have any helpful suggestions for debugging this it would be
appreciated, up to and including rebuilding Evolution or E-D-S, but just
some information on how to get a few debugging messages out of the
WebDAV contacts plugin would be much appreciated.

Regards,
					Andrew McMillan.

#550195#45
Date:
2017-09-24 13:07:44 UTC
From:
To:
Hi,

I seem to have the same problem although it might be another issue as
well. Not sure, so that's why I'm trying here first.

Changing the proxy settings didn't help, after all I never used a proxy
before. However, just like Andrew, I also tried to debug using
Wireshark, and found out that Evolution ignores the configured port
number for my CardDAV setup.
I have configured Evolution to use port 5232 over TLS, however
Wireshark only shows connections to port 443. Oddly enough, changing
the port number for *Cal*DAV does work (also Wireshark only shows
connections to 5232 in this case). Of course, Evolution immediately
notices something is not working as Apache returns status code 405 to
Evolution.

Best,
Tim