I'm having a problem using BLE through dbus where the GATT services don't appear after a BLE device has been found during a scan. What is available through dbus is a Device1 node with the correct address and a Name property of the name which was sent in the advertising beacons - however that's the only node available in the tree. When running with the same BLE dongle (ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0) and same BLE remote device (TI SensorTag 2 CC2650STK) on a different computer I can see all the GATT characteristics in the dbus tree without any problems. The computer with the problem is running on kernel 4.2.0 with bluez 5.34. gatttool works without a problem. Where should I start looking to find out why this is happening? I am a developer; if someone could point me in the direction to begin looking I'll do some investigation. Regards Steven Davies -- 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
