Could that be related to https://code.google.com/p/chromium/issues/detail?id=541606 as well? On Tue, Dec 1, 2015 at 1:04 PM, François Beaufort <beaufort.francois@xxxxxxxxx> wrote: > On Tue, Dec 1, 2015 at 12:55 PM, Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx> wrote: >> Hi François, >> >> On Tue, Dec 1, 2015 at 12:06 PM, François Beaufort >> <beaufort.francois@xxxxxxxxx> wrote: >>> For info, here's some background: >>> https://code.google.com/p/chromium/issues/detail?id=560277 >>> >>> On Tue, Dec 1, 2015 at 11:03 AM, François Beaufort >>> <beaufort.francois@xxxxxxxxx> wrote: >>>> I'm not sure to understand what is happening and I'd love your help there. >>>> >>>> Is the "GattServices" device property still supposed to be updated >>>> once all remote GATT services of the device >>>> have been discovered and exported over D-Bus as mentioned in >>>> http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/device-api.txt#n215 >>>> >>>> If so, does this DBUS messages trace looks good to you: >>>> http://pastebin.com/emxWB4w1? >>> -- >> >> It is a regression caused by restoring the attributes from storage, >> Ive send a patch for that. Btw, it is not recommended to mess up with >> the storage manually if someone is doing this please advise to remove >> the device properly. >> > > What a relief! Thank you Luiz. > > For info, I experienced this with Bluez 5.35. > Will it be part of Bluez 5.37 release? > >> >> -- >> Luiz Augusto von Dentz -- 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
