Bug 2002364

Summary: PrBoom-Plus missing PortMIdi and Alsa Midi support
Product: [Fedora] Fedora Reporter: Simon Putt <lemonzest>
Component: prboom-plusAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 34CC: gwync, jaromir.capik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: prboom-plus-2.6.1-2.fc34 prboom-plus-2.6.1-2.fc35 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-16 19:14:08 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 Simon Putt 2021-09-08 16:01:26 UTC
Description of problem:

when selecting the midi menu options only sdl and fluidsynth work, portmidi and alsa do not function as midi outputs as the buildrequires are not met, also libvorbis and mad are missing

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

2.6.1um

How reproducible:

always

Steps to Reproduce:
1. load prboom-plus from a terminal with a supported wad file
2. attempt to change the midi device from the menus
3. portmidi and alsa will give errors

Actual results:

Exp_RegisterSongEx: Couldn't find preferred music player vorbis player in list
  (typo or support not included at compile time)
Exp_RegisterSongEx: Couldn't find preferred music player mad mp3 player in list
  (typo or support not included at compile time)
db_registersong: couldn't load as tracker
Exp_RegisterSongEx: Couldn't find preferred music player alsa midi player in list
  (typo or support not included at compile time)
Exp_RegisterSongEx: Couldn't find preferred music player portmidi midi player in list
  (typo or support not included at compile time)

Expected results:

for no errors to be present and for portmidi and alsa sequencer options to work.

Additional info:

probably missing alsa-lib-devel, portmidi-devel, libmad-devel and libvorbis-devel not sure of names

Many thanks for your help

Comment 1 Fedora Update System 2021-09-08 16:41:53 UTC
FEDORA-2021-5aa9610fa3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5aa9610fa3

Comment 2 Fedora Update System 2021-09-08 16:41:54 UTC
FEDORA-2021-ac423de009 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ac423de009

Comment 3 Simon Putt 2021-09-08 16:53:11 UTC
I have just installed and tested the new 2.6.1-2 version and all the midi options are working correctly now, thank you for the fast response :)

Comment 4 Fedora Update System 2021-09-08 18:47:18 UTC
FEDORA-2021-5aa9610fa3 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5aa9610fa3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5aa9610fa3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-09-09 17:38:38 UTC
FEDORA-2021-ac423de009 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ac423de009`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ac423de009

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-09-16 19:14:08 UTC
FEDORA-2021-ac423de009 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2021-09-24 20:18:46 UTC
FEDORA-2021-5aa9610fa3 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.