On Tue, Apr 29, 2008 at 09:28:50AM -0400, lance raymond wrote:
> You were right about the user, the cvs compile was done as root, so if I use
> the root user I can run both the btool and msync, but getting an error.
> I re-ran the mysync config's as you wrote as root so mysync will use that
> profile. I had a password set and don't see a msynctool option so the next
> error was related to that, so I removed the password on the device.
That's correct. Passwords are not yet supported for syncing. That will
likely require some opensync support, and I don't think 0.22 has that.
> The btool option gave all the contact info fine, but when I try to sync I
> get 2 different errors, I either get;
> msynctool --sync EvoBarry
> Synchronizing group "EvoBarry"
> 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 01 00 top.......
>
Without seeing more of the conversation, this looks like the Blackberry
was left in an open state by a previously failed sync run. Since
you had a successful barry-sync run in your second example, I'll assume
that you just need to replug your device when this error happens.
The "Required size: 44, RIM Desktop" error happens when the opening
commands don't get the response it expects. The above message probably
means something useful (my guess is that it means "you've already opened
the desktop!") but it hasn't been fully reverse engineered yet, and so
your best bet is to replug the device, so Barry can start with a clean slate.
If this error persists, let me know, and we'll try to do more logging
to see what's going on.
> Member 1 of type evo2-sync had an error while connecting: Unable to open
> anything
This is something you'll have to fix before syncing will happen, and it's
on the evolution side. I noticed it happened in both of your examples.
> <config>
>
> <address_path>/home/lance/.evolution/addressbook/local/system</address_path>
>
> <calendar_path>/home/lance/.evolution/calendar/local/system</calendar_path>
> <tasks_path>/home/lance/.evolution/tasks/local/system</tasks_path>
> </config>
Do these files actually exist? If not, you may need to create a local
address book or something inside Evolution. I forget the actual name, but
I think it was under the first menu option.
> Looked around at the msynctool options didn't see any debug options or where
> the failed logs are.
Opensync logging is done by setting an OSYNC_TRACE environment variable to
a directory where log files will be written. Those logs are *extremely*
verbose, though, so that's a last resort.
export OSYNC_TRACE=/home/cdfrey/software/opensync/0.22/trace_logs
- Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
