Hello! The library conflict with Fedora Core 13 [1] and (more recently) also Debian unstable/testing is serious enough to push out a 1.0.1 minor update. It's tagged and currently goes through the nightly build and testing. I'm a bit in a hurry because tomorrow starts my vacation and I'll be mostly away from computers - yeah! ;-) Before I announce it, can someone install the .rpms on FC 13 and test that SyncEvolution then starts to work again? I uploaded them to: http://downloads.syncevolution.org/tmp/ Other changes (from the NEWS file): * compile fix for FC 13 (and possibly others): use private copy of gdbus (BMC #3556) * sync-ui: prevent overwriting device configs by accident (MBC #3566,1194) Setting up a phone used the template name as config name and overwrote an existing configuration of another phone that was created using that same template. Now the code uses the Bluetooth device name as set on the device and checks for (less likely) collisions. It also sanitizes the name to avoid complicated config names (only relevant when also using the command line). * syncevo-dbus-server: accept 'application/vnd.syncml+xml; charset=UTF-8' for starting an HTTP session (BMC #3554) The redundant charset specification was set by the Funambol Thunderbird client. Because of a literal comparison against 'application/vnd.syncml+xml' the messages were rejected. * config fix: operations on non-peer configs failed (BMC #3157) When running operations on a non-peer configuration (like --restore @default addressbook), the operation fails with [ERROR] <source name>: type 'select backend' not supported * ZYB.com: service goes away end of June 2010, template removed (BMC #3310) * some build (BMC #2586, BMC #3557) and language updates [1] http://bugs.meego.com/show_bug.cgi?id=3556 https://bugzilla.redhat.com/show_bug.cgi?id=606647 -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.