qo: Good detective work. client-id is supposed to be a GUID identifying the system that "owns" the lock on the sync server. The fact that yours is empty could be a problem, as (maybe) your system keeps getting confused that when it sets a lock, it looks like it was made by a *different* system (because the GUIDs don't match).
I'll look into this as soon as I can. By the way, <client-id /> is equivalent XML to <client-id></client-id>, so no worries there. Thanks again for info! -- "fuse: mountpoint is not empty" syncing over ssh https://bugs.launchpad.net/bugs/152978 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
