Elara6331/itd
4
6
Fork 12
Code Issues 8 Pull Requests 1 Projects Releases 11 Wiki Activity

Startup error with bluez 5.65 #22

New Issue
Closed
opened 2022-08-13 21:39:44 +00:00 by mark1250 · 5 comments
mark1250 commented 2022-08-13 21:39:44 +00:00
Copy Link

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.
Elara6331 commented 2022-08-14 03:41:46 +00:00
Owner
Copy Link

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.
Elara6331 commented 2022-08-14 03:43:06 +00:00
Owner
Copy Link

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.
Elara6331 added the
Bug
External
Waiting for Upstream
 labels 2022-08-14 03:44:41 +00:00
Elara6331 commented 2022-08-14 07:07:29 +00:00
Owner
Copy Link

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.
Elara6331 commented 2022-08-19 15:42:40 +00:00
Owner
Copy Link

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.
Elara6331 referenced this issue from a commit 2022-08-19 21:07:23 +00:00
Revert #22 bandaid fix
Elara6331 removed the
Waiting for Upstream
 label 2022-08-19 21:07:48 +00:00
Elara6331 commented 2022-08-19 21:08:06 +00:00
Owner
Copy Link

This issue has now been fixed. Thank you.

This issue has now been fixed. Thank you.
Elara6331 referenced this issue from a commit 2023-04-21 02:08:29 +00:00
Revert #22 bandaid fix
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug
Something is not working
Cantfix
This issue cannot be fixed in ITD
Duplicate
This issue or pull request already exists
Enhancement
New feature
External
This issue is not in ITD
Help Wanted
Need some help
In Progress
This issue is currently being worked on
Invalid
Something is wrong
Question
More information is needed
Waiting
Waiting for something external to be completed to allow completion of issue
Waiting For Info
Waiting for additional information about issue
Waiting for Upstream
Waiting for an upstream project to fix an issue
Wontfix
This won't be fixed
No Label
Bug
External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Elara6331/itd#22
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?