Very interesting suggestion. Yes I think we should do this. Since it's a
feature rather than a bug though, we would either need to request an
exception to get it into 17.10, or wait till 18.04.
** Changed in: bluez (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: bluez (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1713017
Title:
Enable MIDI support
Status in bluez package in Ubuntu:
Triaged
Bug description:
Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
enable Bluetooth MIDI support. This did not seem to be enabled by
default in the build from
https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
MIDI devices, gatttool could talk to them, but no MIDI device was
made; also ldd showed no linkage to libasound.so.2).
After recompiling it with libasound2-dev installed and --enable-midi
in debian/rules, it worked.
Suggestion: add libasound2-dev to bluez dependencies, add --enable-
midi to rules.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp