Hi Patrick, On 22.02.2012 08:33, Mikel Astiz wrote: >> Perhaps that's why it now fails: >> >> Feb 21 16:11:52 pohly-mobl1 bluetoothd[30888]: connect(): Permission >> denied (13) >> >> dbus.exceptions.DBusException: org.ofono.Error.Failed: Operation failed >> >> How do check which kind of pairing is used? I re-paired via the GNOME >> Bluetooth UI, it automatically suggested a PIN and asked whether the >> device showed the same one. > > Well, if you had to enter a pin code, then it's legacy pairing, which > works fine. If you just confirmed a pin code that was given, then it's > SSP, which is affected by a known bug in the kernel. > > You can either (a) patch your kernel, (b) disable SSP, or (c) initiate > the connection from the phone. I suggest the last one since it is > straightforward. > > Also note that you need a running BlueZ agent. You can use the > test/simple-agent script in BlueZ, which will probably ask for > confirmation when the phone tries to initiate the connection.
You seem to suffer from the SSP bug. You can fall back to legacy pairing as Mikel indicated with: sudo hciconfig hci0 sspmode 0 cheers, daniel _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
