Syncevolution fails to connect under ipv6

[Jim Rorie]

Binary package hint: syncevolution

I've been noticing sync evolution has failed to connect to the fuambol server after upgrading to Karmic. Seeing this in the log:

      * [2009-10-30 13:37:51.250] http://my.funambol.com/sync via
        libsoup: Cannot connect to destination

After a bit of research I turned off ipv6 by adding this to my grub boot command line:

ipv6.disable=1

Syncevolution now connects. Let me know what other logs I can provide.
-----------

jfrorie@medusa:~$ syncevolution --version
SyncEvolution 0.9

Linux medusa 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

i libsoup-gnome2.4-1 - an HTTP library implementation in C -- GNOME support li
p libsoup-gnome2.4-dev - an HTTP library implementation in C -- GNOME support de
p libsoup2.2-8 - an HTTP library implementation in C -- Shared library
p libsoup2.2-dev - an HTTP library implementation in C -- Development file
p libsoup2.2-doc - an HTTP library implementation in C -- API Reference
i libsoup2.4-1 - an HTTP library implementation in C -- Shared library
p libsoup2.4-dbg - an HTTP library implementation in C -- debugging symbol
p libsoup2.4-dev - an HTTP library implementation in C -- Development file
p libsoup2.4-doc - an HTTP library implementation in C -- API Reference

i syncevolution - Evolution data synchronization program using SyncML
pB syncevolution-evolution - SyncEvolution SyncML Client
p syncevolution-evolution-2.12 - SyncEvolution is now packaged so that "syncevolution-ev
p syncevolution-evolution-2.6 - SyncEvolution is now packaged so that "syncevolution-ev
p syncevolution-evolution-2.8 - SyncEvolution is now packaged so that "syncevolution-ev

[Jim Rorie (jfrorie)]

Submission determined to be duplicate. Now pointing to root bug.

[Frank (luxeven)]

Thanks for the workaround. I had the same problem with libsoup and disabling IPv6 brought syncevolution (I am using it with the GUI genesis) back to life.

[Dries Decock (dries-decock-telenet)]

I had the same issue. I use IPv6 where possible, so disabling IPv6 was not an option. I just added the IPv4 address of my sync server to my /etc/hosts file to work around this issue.