Startup error with bluez 5.65 #22

Closed
opened 4 months ago by mark1250 · 5 comments

I'm on PostmarketOS Edge - SXMO sway on the Pinephone A64.

bluez has been updated from 5.64 to 5.65.

When I attempt to start itd, I'm seeing the following.

pine64-pinephone:~/Downloads/itd$ itd
4:30PM FTL Error connecting to InfiniTime error="MapToStruct: Field not found: Bonded"

I've been using version 0.0.6 on bluez 5.64 and it has been working very well with superd.

Thanks for making this software.

I'm on PostmarketOS Edge - SXMO sway on the Pinephone A64. bluez has been updated from 5.64 to 5.65. When I attempt to start itd, I'm seeing the following. ``` pine64-pinephone:~/Downloads/itd$ itd 4:30PM FTL Error connecting to InfiniTime error="MapToStruct: Field not found: Bonded" ``` I've been using version 0.0.6 on bluez 5.64 and it has been working very well with superd. Thanks for making this software.
Owner

This is most likely the result of a new breaking change in BlueZ. This has happened before. I'll need to update the BlueZ library.

This is most likely the result of a new breaking change in BlueZ. This has happened before. I'll need to update the BlueZ library.
Owner

This issue is being tracked upstream at muka/go-bluetooth#168. I can't do much until support for 5.65 is added.

This issue is being tracked upstream at [muka/go-bluetooth#168](https://github.com/muka/go-bluetooth/issues/168). I can't do much until support for 5.65 is added.
Arsen6331 added the Bug External Waiting for Upstream labels 4 months ago
Arsen6331 referenced this issue from a commit 4 months ago
Owner

This issue should now be fixed with a temporary bandaid solution until proper support is added for 5.65. I've opened an issue and PR upstream that should prevent issues like this from happening in the future. This issue should remain open until proper support for 5.65 is added and my PR is merged.

This issue should now be fixed with a temporary bandaid solution until proper support is added for 5.65. I've opened an issue and PR upstream that should prevent issues like this from happening in the future. This issue should remain open until proper support for 5.65 is added and my PR is merged.
Owner

My PR has been merged and BlueZ 5.65 support has been added upstream. I will test and if it works, I will close this issue.

My PR has been merged and BlueZ 5.65 support has been added upstream. I will test and if it works, I will close this issue.
Arsen6331 referenced this issue from a commit 3 months ago
Arsen6331 closed this issue 3 months ago
Arsen6331 removed the Waiting for Upstream label 3 months ago
Owner

This issue has now been fixed. Thank you.

This issue has now been fixed. Thank you.
Sign in to join this conversation.
Loading…
There is no content yet.