http://bugzilla.moblin.org/show_bug.cgi?id=2069
--- Comment #10 from pohly <[email protected]> 2010-03-15 03:32:45 PST --- (In reply to comment #9) > > This is what syncevolution command line prints when phone is out of range: > > [ERROR] ObexTransport: Transport Exception in sdp_source_cb > > [ERROR] TransportException while sending SAN package > > [ERROR] Server Alerted Sync init failed > > What kind of status do you expect in this case? Does the command line record > it > as expected? The SAN code was changed so that a transport failure now gets reported as one, instead of catching the transport exception and rethrowing a generic error (the root cause for the 500 status). -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
