I was trying to configure media-sound/fluidsynth-2.3.4-r1 to enable MIDI in DOSbox, but I got an error when starting it. The systemd log showed: Apr 27 10:02:50 op7010 fluidsynth[3045]: unknown command: SOUND_FONT=/usr/share/sounds/sf2/FluidR3_GM.sf2 (try help) Apr 27 10:02:50 op7010 fluidsynth[3045]: unknown command: OTHER_OPTS=-a pipewire (try help) Apr 27 10:02:50 op7010 fluidsynth[3045]: Failed to early-execute command configuration file '/etc/fluidsynth.conf' Apr 27 10:02:50 op7010 fluidsynth[3045]: fluidsynth: Using PipeWire audio driver Apr 27 10:02:50 op7010 fluidsynth[3045]: *** impl_ext_end_proxy called from wrong context, check thread and locking: Operation not permitted Apr 27 10:02:50 op7010 fluidsynth[3045]: *** impl_ext_end_proxy called from wrong context, check thread and locking: Operation not permitted Apr 27 10:02:51 op7010 fluidsynth[3045]: NOTE: FluidSynth compiled without network support, unable to start server! Apr 27 10:02:51 op7010 fluidsynth[3045]: FluidSynth runtime version 2.3.4 Apr 27 10:02:51 op7010 fluidsynth[3045]: Copyright (C) 2000-2023 Peter Hanappe and others. Apr 27 10:02:51 op7010 fluidsynth[3045]: Distributed under the LGPL license. Apr 27 10:02:51 op7010 fluidsynth[3045]: SoundFont(R) is a registered trademark of Creative Technology Ltd. Apr 27 10:02:51 op7010 systemd[1169]: fluidsynth.service: Failed with result 'protocol'. I recompiled fluidsynth with the network USE flag enabled, and it then started and worked without a problem. Apparently fluidsynth uses sockets when connecting to pipewire or pulseaudio and thus requires network support to be enabled to work with them. So it seems network support should be required if either of those are enabled or that a message should be displayed to the user in the event that it is foreseeable that some users might not want to use fluidsynth with pipewire or pulseadio even if they are present on the system. Reproducible: Always
