Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
wrong version requirement for BlueZ on Linux
See original GitHub issueSince 94163fa1d4929b243311988c420b2bcffb204270 (#61), write_gatt_char requires at least BlueZ 5.46, because AcquireWrite was not introduced before.
The current version checking logic in __init__.py and the readme files all claim that 5.43 is sufficient.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Bluez Installation - configuration error for DBUS 1.6 - Ask Ubuntu
I am trying to install bluez 5.2 libraries on Ubuntu 12.04. while running ./configure , I received error for GLib2. 0, I was...
Read more >Bluetooth - ArchWiki
Bluetooth is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. In Linux, the canonical ...
Read more >BlueZ
BlueZ. Official Linux Bluetooth protocol stack ... Since version 0.3.59, PipeWire supports LE Audio's Basic Audio Profile (BAP) for ... Defaults to false....
Read more >Regretfully ditching linux...because Bluetooth Midi doesn't ...
I reported back that I removed the existing version of Bluez and re-installed it as best I could following the instructions.
Read more >Upgrade BlueZ on Ubuntu for use with Home Assistant ...
Failed to start BlueTooth: [org.bluez.Error. ... This turned out to be true, the version installed on my Ubuntu server was 5.37, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’d argue that the default
response=Falsedid not really make sense, because that’s the stricter version requirement - but then again, with the exception in #138, chances are higher for people to find the parameter.@afflux In my mind, the
response=Falsewas the simpler choice and thus the default behaviour. The other OS backends have no such version requirement demands, and I don’t want to change default behaviour for all of them.It is now a regrettable byproduct of a choice I made in the advent of this project.