Bug 1292286 - sysex parsing is broken
sysex parsing is broken
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: fluidsynth (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Brendan Jones
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-16 17:17 EST by Stas Sergeev
Modified: 2016-07-19 14:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 14:36:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
the fix (1.07 KB, application/mbox)
2015-12-16 17:17 EST, Stas Sergeev
no flags Details

  None (edit)
Description Stas Sergeev 2015-12-16 17:17:33 EST
Created attachment 1106542 [details]
the fix

Description of problem:
fluidsynth has sysex parsing broken.
The attached patch is needed to fix it.

Version-Release number of selected component (if applicable):
fluidsynth-1.1.6-5.fc22.x86_64

How reproducible:
Not easily... You need to use fluidsynth API in your
app. Or maybe some very unusual midi file with sysexes.
But I am reproducing that only inside my app.

Actual results:
sysex events contain only 1 byte.

Expected results:
sysexes parsed fully.

Additional info:
I've also opened an upstream report:
http://sourceforge.net/p/fluidsynth/tickets/150/
And I wouldn't bother downstream, but it seems the
tracker is inactive, and there were no releases for
many years. So I am filling the bug also here.
Comment 1 Fedora End Of Life 2016-07-19 14:36:25 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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

Note You need to log in before you can comment on or make changes to this bug.