Description of problem: Events with no end-time cause sync failure. Appointments sync fine. Events created on device have midnight-midnight times and sync fine. Events created in Evolution events marked as "all-day" cause the sync to fail with error message that not all items could be written. Results the same in msynctool and multisync-gui. Have tried on various models and ages of blackberry devices and several hosts. Version-Release number of selected component (if applicable): barry-opensync: 0.17-0.6.20101126git.fc14 barry-opensync: 0.17-0.3.20100720git.fc14 How reproducible: Always Steps to Reproduce: 1. Create an all-day event in Evolution 2. Attempt to sync using msynctool or multisync-gui 3. Actual results: Failed sync Expected results: Successful sync Additional info:
There is a update in updates-testing that is going to be 0.17 eventually... can you verify that the problem still exists? Though I'm not sure if that will fix it as it may be an opensync issue. I'll notify upstream as well about the issue.
Installed newest barry and barry plugin packages from testing. Wiped blackberry, started with blank calendar in evolution. Ran multisync-gui calendar only. Success. Added an appointment with start and end times. Osplugin aborted. Cleared all data tried again with msynctool. Initial sync successful. Added an appointment with start and end time and the sync failed. Repeated with an all-day event, also failed. Output of failed msynctool below. [dfagan@fagan01 ~]$ msynctool --sync test Synchronizing group "test" Member 2 of type evo2-sync just connected Member 1 of type barry-sync just connected All clients connected or error Member 1 of type barry-sync just sent all changes Received an entry 20110125T050019Z-2930-1000-1-4.local with data of size 4 from member 2 (evo2-sync). Changetype ADDED Member 2 of type evo2-sync just sent all changes All clients sent changes or error All conflicts have been reported Member 2 of type evo2-sync committed all changes. Error writing entry 20110125T050019Z-2930-1000-1-4.local to member 1 (barry-sync): Broken Pipe Mapping Write Error: Broken Pipe Member 1 of type barry-sync had an error while commiting changes: Broken Pipe All clients have written Member 1 of type barry-sync had an error while calling sync done: Broken Pipe Member 1 of type barry-sync had an error while disconnecting: Broken Pipe Member 2 of type evo2-sync just disconnected All clients have disconnected The sync failed: Unable to finish the sync for one of the members Error while synchronizing: Unable to finish the sync for one of the members
Thanks so much for working with me on this. Often we get a bug report, but no responses afterwards. Upstream is super responsive - I usually hear from them within a day or two and they actively work at finding the issue. So I'll have more information/questions for you as this process moves along.
Have you tried the latest releases?? I'm building the 0.17.0 release today, but you should be able to test the current one as well. Please provide some feedback otherwise I'll have to close this.
Sorry if I missed something, but I did not realize a new version was available. I just installed barry-opensync-0.17-0.6.20110126git.fc14.i686 from the Testing Updates repo (along with all related dependencies). Have run several tests and all is looking good so far. Thanks!
fixed in barry-opensync-0.17-0.6.20110126git.fc14.i686