On Wed, Oct 20, 2010 at 11:17 AM, Igor pesando <ipesando@xxxxxxxxx> wrote: > The issue I have is therefore associated with blueman: > when you switch off the adapter with blueman and then kill blueman-applet > hciconfig hci0 up does not work and returns an error (Can't init > device hci1: Unknown error 132 (132) ) > and sometimes > dbus-send and test-adapter do the same ( > dbus.exceptions.DBusException: org.bluez.Error.Failed: Unknown error > 132) > while blueman-applet can solve the problem if restarted. Might not be related but... it could be that RFKILL has disabled the device. Run "rfkill list" and see if is either hard or soft blocked. If it is, unblock it with "rfkill unblock <id>". I've seen many times bluetoothd blocking devices on shutdown, maybe because it thinks the device is blocked during start. Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil -- 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
