On Mon, 2011-01-17 at 09:24 +0100, Patrick Ohly wrote:
Note that SyncEvolution automatically finds the right channel. There
should never be a need to specify it explicitly.
Hey Patrick. If I remove the explicit channel specifier from the
bluetooth address in the syncURL field, I get the following while being
prompted on the phone to accept a connection and hitting yes...
$ syncevolution nokia_e71
[INFO] todo: inactive
[INFO] memo: inactive
[INFO] calendar+todo: inactive
[INFO] calendar: inactive
[INFO] Server sending SAN
[ERROR] OBEX Request 3 got a failed response Forbidden
[INFO] Server sending SAN
[ERROR] OBEX Request 3 got a failed response Forbidden
[ERROR] ObexTransprotAgent: Underlying transport error
Synchronization failed,
see /home/kip/.cache/syncevolution/nokia__e71-2011-01-19-16-48/syncevolution-log.html for
details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Wed Jan 19 16:48:47 2011, duration 0:17min |
| external transport failure (local, status 20043) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: OBEX Request 3 got a failed response Forbidden
[ERROR] command line execution failure
I've attached the log as well.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com