Bluetoothd errors out after a few button presses
CheapB opened this issue · 6 comments
It works for a a while en then I get this:
bluetoothd[1321]: src/service.c:change_state() 0x108330: device 80:E4:DA:70:0E:A1 profile :1.20/org/flic/00_1A_7D_DA_71_0B/f02adfc0-26e7-11e4-9edc-0002a5d5c51bstate changed: disconnected -> unavailable (0)
bluetoothd[1321]: src/gatt-database.c:profile_device_remove() :1.20/org/flic/00_1A_7D_DA_71_0B/f02adfc0-26e7-11e4-9edc-0002a5d5c51b removed
bluetoothd[1321]: src/service.c:btd_service_unref() 0x108330: ref=0
bluetoothd[1321]: src/gatt-client.c:btd_gatt_client_service_removed() GATT Services Removed - start: 0x0010, end: 0x0016
bluetoothd[1321]: src/gatt-client.c:unregister_service() Removing GATT service: /org/bluez/hci0/dev_80_E4_DA_70_0E_A1/service0010
bluetoothd[1321]: src/gatt-client.c:unregister_characteristic() Removing GATT characteristic: /org/bluez/hci0/dev_80_E4_DA_70_0E_A1/service0010/char0011
bluetoothd[1321]: src/gatt-client.c:notify_client_unref() owner :1.20
bluetoothd[1321]: src/gatt-client.c:notify_client_free() owner :1.20
bluetoothd: src/shared/gatt-client.c:2962: bt_gatt_client_unregister_notify: Assertion `notify_data->chrc->notify_count > 0' failed.
This is a bug in bluez. I have notified the developers about this issue and hopefully it will be resolved soon!
The good people developing bluez sent me some patches today and hopefully this will resolve this issue. Im running a test over night to see if it's so.
Hi @fabianbergmark how is the testing going?
@richbeales try these patches out: http://thread.gmane.org/gmane.linux.bluez.kernel/66537
I have been running them successfully for 2 days!
I now have the patched bluez up and running and the above error has not surfaced for the last hour. Now there is still some inconsistency in the response time that will will look into if this otherwise stays stable. Thanks!
Seems to be stable now. i am closing this in a few days unless more comments/issues are surfacing