Bug 2082559

Summary:	bluez midi support
Product:	[Fedora] Fedora	Reporter:	Joakim Verona <joakim>
Component:	bluez	Assignee:	Gopal krishna tiwari <gopalkrishna.tiwari>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bnocera, code, colin, dwmw2, gopalkrishna.tiwari, pbrobinson, spacewar, ycollette.nospam
Target Milestone:	---	Keywords:	Reopened, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-13 17:56:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joakim Verona 2022-05-06 12:14:32 UTC

Description of problem:

Bluez is not compiled with MIDI support


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Try to connect a Bluetooth MIDI device to a Fedora machine
2.
3.

Actual results:
The device connects, but is not a correct MIDI device

Expected results:
The device should connect and show up as a MIDI device with aconnect -io

Additional info:

Bluez has MIDI support, but its not enabled by default, so the Fedora packaging thus lacks MIDI support in Bluez.

It is fairly easy to enable, a --enable-midi configure flag for bluez, and its easy to test to enable this flag to the spec file.

Then to actually test that it works in practice you need a Bluetooth MIDI device, such as the Korg Nanokey studio.

Then bluetoothd will need some new privs from selinux. After this is done you can verify the device shows up with aconnect -io, and then you can play an instrument in yoshimi for example, with the now wireless Nanokey studio.

It would be neat if this could be added to the standard packaging, so you dont need to compile yourself and would enhance Fedora for creative usage.

Comment 1 Peter Robinson 2022-08-31 08:03:56 UTC

I started to have a look at this. At first I thought it would just be an addon binary we could put in a sub package like the BT headset audio or cups but it appears not and it links directly into the core daemon which means we pull in the audio deps too. Will need some thought.

Comment 2 Ben Cotton 2022-11-29 18:52:50 UTC

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-12-13 17:56:26 UTC

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Peter Robinson 2023-06-02 08:12:19 UTC

*** Bug 2211730 has been marked as a duplicate of this bug. ***

Comment 5 ycollet 2023-06-02 08:20:02 UTC

Yes, that was the way I checked that bluetoothd has the midi support: ldd /usr/libexec/bluetoothd has a dependency on libasound.so

Maybe you can resolve this by a double build. A first build without support of bluetooth midi and generates the standard package and another one with midi support and this one when installed replace the other one ?

Comment 6 Peter Robinson 2023-06-02 08:38:48 UTC

A double build is an absolute non starter, twice the work, and support would be a nightmare.

Comment 7 ycollet 2023-07-20 08:16:59 UTC

Still no solution for the midi support ? 
Most of the bluetooth device used are audio device. So adding the support for midi in bluez and having an alsa deps is not a big deal because alsa will be already there for most of these bluetooth devices ...

Comment 8 Peter Robinson 2023-07-20 08:40:09 UTC

(In reply to ycollet from comment #7)
> Still no solution for the midi support ?

No, else this would be closed.

> Most of the bluetooth device used are audio device. So adding the support
> for midi in bluez and having an alsa deps is not a big deal because alsa
> will be already there for most of these bluetooth devices ...

Not true, firstly most audio devices like headphones/speakers etc use pipewire/pulseaudio etc for audio and just use bluez for the setup. These are already supported and working without alsa linked into bluez. Also you have input devices, which likely outnumber audio devices considerably, not to mention the millions of "IoT devices" like sensors...