Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it

[Patrice Duroux <patrice.duroux@gmail.com>]

Package: fluidsynth
Version: 2.4.0-1
Followup-For: Bug #1053245

Hi,

Some progress have been made in 2.4.0-1 packaging on this issue as its unit
service is now in userland.
But there is still an issue opening a user session on my Sid system with a
GNOME desktop:

$ systemctl --user status fluidsynth
× fluidsynth.service - FluidSynth Daemon
     Loaded: loaded (/usr/lib/systemd/user/fluidsynth.service; enabled; preset:
enabled)
     Active: failed (Result: protocol) since Sun 2024-12-29 11:47:41 CET; 6min
ago
 Invocation: b91cda23db4d4466b0c1dab6be5d06a6
       Docs: man:fluidsynth(1)
    Process: 2647 ExecStart=/usr/bin/fluidsynth -is $OTHER_OPTS $SOUND_FONT
(code=exited, status=0/SUCCESS)
   Main PID: 2647 (code=exited, status=0/SUCCESS)
   Mem peak: 169.5M
        CPU: 899ms

déc. 29 11:47:36 kos-moceratops fluidsynth[2647]: Continuing without it.
déc. 29 11:47:36 kos-moceratops fluidsynth[2647]: fluidsynth: warning: Failed
to set thread to high priority
déc. 29 11:47:40 kos-moceratops fluidsynth[2647]: fluidsynth: warning: Failed
to set thread to high priority
déc. 29 11:47:41 kos-moceratops fluidsynth[2647]: FluidSynth runtime version
2.4.0
déc. 29 11:47:41 kos-moceratops fluidsynth[2647]: Copyright (C) 2000-2024 Peter
Hanappe and others.
déc. 29 11:47:41 kos-moceratops fluidsynth[2647]: Distributed under the LGPL
license.
déc. 29 11:47:41 kos-moceratops fluidsynth[2647]: SoundFont(R) is a registered
trademark of Creative Technology Ltd.
déc. 29 11:47:41 kos-moceratops systemd[2619]: fluidsynth.service: Failed with
result 'protocol'.
déc. 29 11:47:41 kos-moceratops systemd[2619]: Failed to start
fluidsynth.service - FluidSynth Daemon.
déc. 29 11:47:41 kos-moceratops systemd[2619]: fluidsynth.service: Consumed
899ms CPU time, 169.5M memory peak.


And (re)starting it after the session is opened is ok to me.

My theory is that it seems somehow it requires more than pipewire as declared
in the service file.
The trouble is that it is supposed to have 'pipewire' as a possible audio
driver:

$ fluidsynth -a help
-a options (audio driver):
   'alsa','file','jack','oss','pipewire','pulseaudio','sdl2'

Could this be a problem due to audio driver initialization in fluidsynth when
none is defined by configuration?
(OTHER_OPTS is commented in /etc/default/fluidsynth and no
~/.config/fluidsynth)

Or maybe there is something to document in a README.Debian file.

Regards,
Patrice


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.6-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fluidsynth depends on:
ii  init-system-helpers   1.67
ii  libc6                 2.40-4
ii  libfluidsynth3        2.4.0-1
ii  libglib2.0-0t64       2.82.4-1
ii  libpipewire-0.3-0t64  1.2.7-1
ii  libsdl2-2.0-0         2.30.10+dfsg-1
ii  libsystemd0           257.1-5

Versions of packages fluidsynth recommends:
ii  qsynth  1.0.2-1

fluidsynth suggests no packages.

-- no debconf information