-
Notifications
You must be signed in to change notification settings - Fork 18
fliclib does not work with the current bluez master #34
Copy link
Copy link
Open
Description
One of the recent commits of bluez seem to break something up, it's not possible to connect buttons anymore. Log when trying to connect:
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Connecting to: 80:E4:DA:70:CC:DD
Disconnecting from: 80:E4:DA:70:CC:DD
Disconnected from: 80:E4:DA:70:CC:DD
Moving back to Bluez 5.37 solves the problem. Although fliclib is still in beta and shouldn't be used for operational purposes, building bluez against master makes the behaviour very unpredictable and tracking of problems very hard as everything could change when a new commit comes in. Furthermore, many users will have many different bluez versions depending on the time they built it. Maybe it's better to recommend using bluez 5.37 instead of master?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels