Skip to content

fliclib does not work with the current bluez master #34

Description

@pfink

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions