Re: [fluid-dev] fluidsynth 2.1.1 not creating a server

[Marcus Weseloh]

Hi Knute,

you say that you used a user unit file file in .config/systemd/user/,
but the output from the status command is a report from a system unit
file in /lib/systemd/system/fluidsynth.service.

If you want to use user-unit files, you need to prefix all systemctl
commands with --user. So you could try the following:

First make sure your system-wide fluidsynth unit is stopped:
$ sudo systemctl stop fluidsynth

Then reload your user-systemd just to be on the safe side:
$ systemctl --user daemon-reload

Then try to activate your user-unit and check it's status:
$ systemctl --user start fluidsynth
$ systemctl --user status fluidsynth

Cheers
Marcus


Am Do., 6. Aug. 2020 um 23:08 Uhr schrieb Knute Snortum <ksnortum@gmail.com>:
>
> Thanks, Ceresa, I read that whole thread but it doesn't seem to apply
> to my situation.
>
> I am on Ubuntu 20.04, using systemd now to try to start FluidSynth.  I
> learned that PulseAudio won't start as root, so I added my service to
> ~/.config/systemd/user.  It looks like this:
>
> [Unit]
> Description=FluidSynth launched in server mode
> After=sound.target
>
> [Service]
> ExecStart=/usr/bin/fluidsynth -a pulseaudio -m alsa_seq -i -l -s -p
> FluidSynth /usr/share/sounds/sf2/FluidR3_GM.sf2
>
> [Install]
> WantedBy=default.target
>
> But when I do a systemctl status fluidsynth, I see this:
>
> fluidsynth.service - FluidSynth
>      Loaded: loaded (/lib/systemd/system/fluidsynth.service; enabled;
> vendor preset: enabled)
>      Active: failed (Result: exit-code) since Thu 2020-08-06 08:47:37
> PDT; 5h 6min ago
>     Process: 838 ExecStart=/usr/bin/fluidsynth -a pulseaudio -m
> alsa_seq /usr/share/sounds/sf2/FluidR3_GM.sf2 (code=exited,
> status=255/EXCEPTION)
>    Main PID: 838 (code=exited, status=255/EXCEPTION)
>
> Aug 06 08:47:36 knute-NUC7PJYH systemd[1]: Started FluidSynth.
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: fluidsynth: error:
> Failed to create PulseAudio connection
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: Failed to create the
> audio driver
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: FluidSynth runtime version 
> 2.1.1
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: Copyright (C)
> 2000-2020 Peter Hanappe and others.
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: Distributed under the
> LGPL license.
> Aug 06 08:47:37 knute-NUC7PJYH fluidsynth[838]: SoundFont(R) is a
> registered trademark of E-mu Systems, Inc.
> Aug 06 08:47:37 knute-NUC7PJYH systemd[1]: fluidsynth.service: Main
> process exited, code=exited, status=255/EXCEPTION
> Aug 06 08:47:37 knute-NUC7PJYH systemd[1]: fluidsynth.service: Failed
> with result 'exit-code'.
>
> Any ideas why the PulseAudio connection fails?
>
> ---
> Knute Snortum
> (via Gmail)
>
>
> ---
> Knute Snortum
> (via Gmail)
>
>
> On Wed, Aug 5, 2020 at 2:41 PM Ceresa Jean-Jacques
> <jean-jacques.ceresa@orange.fr> wrote:
> >
> > Hi,
> >
> >
> >
> > >How would you start FluidSynth at startup automatically? -
> >
> >
> >
> > Here possible solution.
> >
> > https://lists.nongnu.org/archive/html/fluid-dev/2020-01/msg00032.html
> >
> > jjc
> >
> >
> >
> > _______________________________________________
> > fluid-dev mailing list
> > fluid-dev@nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/fluid-dev
>
> _______________________________________________
> fluid-dev mailing list
> fluid-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fluid-dev