--- On Sat, 25/6/11, Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> wrote: > The typical way to debug bluetooth issues is: > 1. add debug flag "-d" to bluetoothd command line and then > review system log There is some strange stuff going on: Jun 25 19:48:27 venus udevd[25268]: failed to execute '/usr/local/sbin/bluetoothd' '/usr/local/sbin/bluetoothd --udev': No such file or directory bluetoothd is in /usr/sbin not /usr/local/sbin. I don't know how to switch that. Jun 25 19:48:41 venus bluetoothd[916]: input-headset driver probe failed for device 00:1F:CC:C2:E4:86 I don't know what that is. I don't have a bluetooth headset. That is the address of my mobile phone. Mark. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html