Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it
On Thu, 2 Nov 2023 23:05:28 +0100 at46 <at46n@t-online.de> wrote:
> I had the same problem and it took me quite some time to find that
> fluidsynth was the root cause of this. Fluidsynth was installed as
new
> dependency from lutris 0.5.14 and blocked my sound device each
~second
> boot.
>
> @Patrick I could check the status with "systemctl --user status
> fluidsynth" and disable it with "sudo systemctl --global disable
> fluidsynth.service"
>
fluidsynth and pulseaudio are both user session services. They are
started at login (ie not at boot).
>From /usr/lib/systemd/user/fluidsynth.service, it seems only pipewire
is handled, ie not pulseaudio:
"
[Unit]
Description=FluidSynth Daemon
Documentation=man:fluidsynth(1)
After=sound.target
After=pipewire.service
[Service]
# added automatically, for details please see
#
https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort
ProtectSystem=full
ProtectHome=read-only
ProtectHostname=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=true
# end of automatic additions
# required in order for the above sandboxing options to work on a user
unit
PrivateUsers=yes
Type=notify
NotifyAccess=main
EnvironmentFile=/etc/default/fluidsynth
EnvironmentFile=-%h/.config/fluidsynth
ExecStart=/usr/bin/fluidsynth -is $OTHER_OPTS $SOUND_FONT
[Install]
WantedBy=default.target
"
Seems you are running native pulseaudio and not pipewire-pulse.
Could you try adding pulseaudio.service "pulseaudio.service" to the
"After" directive of fluidsynth.service, via systemctl --user edit
fluidsynth.service by writing in the editor that will open:
"
[Unit]
After=pipewire.service pulseaudio.service
"
then running:
systemctl --user daemon-reload
and logout/login, then check that pulseaudio see your audio device?
Still, fluidsynth should be running, so the issue might be otherwise.
At least with pipewire/pipewire-pulse/fluidsynth I have all of them up
simultaneously for the whole user session.
Best regards,
Alban
Reply to: