On Tue, Sep 15, 2009 at 10:48:48PM -0400, Ellen Oler wrote: > el...@ellens-netbook:~$ evolution --force-shutdown > el...@ellens-netbook:~$ msynctool --sync EvoBarry > > The first time I ran this it seemed to begin OK and transmit records, except > that it hung up after a message - something like - all clients have sent > changes or error.
As your other messages noted, this is likely due to conflict resolution. You can check 'top' output to see if osplugin or osengine or something opensync related is chewing up CPU time. If it is, just wait for a while. It may also help to zap one side of the equation, recreate your config, and start over, so that conflicts are not needed. Conflict resolution isn't the greatest with Opensync 0.22. > I waited a while, control-C'ed the operation and tried again. > Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 > 00000000: 00 00 1a 00 09 ff 00 07 52 49 4d 20 44 65 73 6b ........RIM > Desk > 00000010: 74 6f 70 00 00 00 00 00 02 00 top....... > > Member 2 of type barry-sync had an error while connecting: Bad packet size. > Packet: 26. DataSize(): 26. Required size: 44 These are often related... if Barry can't shutdown the connection properly, the Blackberry gets into a state that Barry doesn't yet know how to get it out of. Simply replygging the device usually solves it. And if the apps shutdown properly, you shouldn't run into this error too often. - Chris ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
