ubuntustudio-bugs team mailing list archive
-
ubuntustudio-bugs team
-
Mailing list archive
-
Message #11861
[Bug 2058799] Re: a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them
Reinaert,
The patch has been uploaded to Noble (future 24.04). Can you come up
with a simple, step-by-step procedure for testing in previous versions
and be willing to do the tests when the SRU team accepts? I have the
feeling these are fairly hardware-specific requirements and not just
anyone will be able to test. I, for one, will be unable to test as I
don't have any two MIDI hardware that is identical.
** Changed in: a2jmidid (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2058799
Title:
a2jmidid doesn't handle midi interfaces with two or more identical
port names correctly and fails to expose them
Status in a2jmidid package in Ubuntu:
Fix Committed
Status in a2jmidid source package in Jammy:
In Progress
Status in a2jmidid source package in Mantic:
In Progress
Status in a2jmidid source package in Noble:
Fix Committed
Bug description:
This issue has been solved in 2019 in a2jmidid:
https://github.com/jackaudio/a2jmidid/pull/5
It's been described in various places:
https://linuxmusicians.com/viewtopic.php?t=24822
Could you please include this in the packages? It basically boils down to this four letter change in port.c:
119c119
< "%s [%d] (%s): [%d] %s",
---
> "%s [%d] (%s): %s",
Kind regards,
Reinaert
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/2058799/+subscriptions
References