On Tue, 2010-08-03 at 12:39 -0700, Stephan Janz wrote: Can you update to the latest stable version, 1.0.1? Then please send a copy of the syncevolution-log.html file of a regular sync which creates duplicates, either here or to syncevolution(a)lists.intel.com (will be treated confidential). -- 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.

On Tue, 2010-08-03 at 13:18 -0700, Stephan Janz wrote: You need to copy the files to /usr, then ensure that syncevo-dbus-server gets restarted. But note that there are also .rpms and .debs available for 1.0.1 - you shouldn't need the .tar.gz. -- 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.

On Wed, 2010-08-04 at 00:09 -0700, Stephan Janz wrote: Use the "stable" repository instead of the "unstable" one. Hmm, should I publish stable versions in both repos? Yes, done for 1.0.1. -- 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.

On Mi, 2010-08-04 at 16:40 +0100, Stephan Janz wrote: Did you restart syncevo-dbus-server? What does "ps -ef | grep syncevo-dbus-server" say, and where does that file really come from ("dpkg -S <file>")? You might be running into a bug in the server implementation which has already been fixed for a while. The bug was related to not storing meta information correctly, and your log shows that the server indeed does something weird based on that meta data (multiple local items all mapped to same temporary ID #61). To recover from this, please wipe out the ".server.ini" files inside your config, see: .config/syncevolution/default/peers/<config name>/sources/addressbook/.server.ini Then do a refresh from client or server (depending on where you have clean data), or a slow sync if you cannot afford to wipe out one side. -- 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.