Priority medium
Bug ID 57340
CC syncevolution-issues@syncevolution.org
Assignee syncevolution-issues@syncevolution.org
Summary Wrong HashCode after sync if home is mounted over NFS
Severity normal
Classification Unclassified
OS Linux (All)
Reporter dbet1@gmx.net
Hardware x86 (IA32)
Status NEW
Version 1.3
Component SyncEvolution
Product SyncEvolution

I have two machines with Ubuntu 10.04. Machine A is the master. On machine B my
home is mounted with NFS from Machine A. Synchronisation works fine on machine
A, and also on machine B. But after sync on machine B on machine A it does not
work any more. I am logged in at a time on one machine only of course.

I have found out that the hash code in the file
~/.config/syncevolution/default/peers/memotoo/.internal.ini is much more
greater after syncing on machine B then after syncing on machine A. I then open
.internal.ini and delete the hash code. After that syncevolution creates a new
hash. From then sync on machine A works fine until I sync the next time from
machine B.

Messages from syncevolution on the command line on machine A during sync after
sync on machine B:
[ERROR] error code from SyncEvolution fatal error (local, status 10500)
~/.config/syncevolution/default/peers/memotoo/.internal.ini: HashCode =
10594356235175291768: cannot parse value

machine A: HashCode = 1435593592
machine B: HashCode = 10594356235175291768

Because I use auto sync and the home is NFS mounted, the auto sync also occurs
on machine B. Thus the hash code is wrong after that.


You are receiving this mail because: