FS#67955 - [fluidsynth] enabling service does not work

Attached to Project: Arch Linux
Opened by Jakob Jarmar (jarmar) - Monday, 21 September 2020, 17:44 GMT
Last edited by David Runge (dvzrv) - Monday, 21 September 2020, 19:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After enabling, fluidsynth.service does not start automatically with the user session.

I believe the issue is that the unit file references multi-user.target, and that this target does not exist for user instances of systemd (it is not listed in the "Special User Units" section of man 7 systemd.special). My understanding is that default.target should be used instead (quoting the manpage):

> default.target
> This is the main target of the user session, started by default. Various
> services that compose the normal user session should be pulled into this
> target. In this regard, default.target is similar to multi-user.target in
> the system instance, but it is a real unit, not an alias.

If I override the unit file with WantedBy=default.target, fluidsynth does start automatically.

Additional info:
* package version: 2.1.5-1

Steps to reproduce:
1) Install fluidsynth
2) Run systemctl --user enable fluidsynth.service
3) Start a new user session
4) Fluidsynth does not start automatically with the user session
This task depends upon

Closed by  David Runge (dvzrv)
Monday, 21 September 2020, 19:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with fluidsynth 2.1.5-2
Comment by David Runge (dvzrv) - Monday, 21 September 2020, 19:01 GMT
@jarmar: Thanks for the report!

I have opened an upstream pull request [1] and will apply this in a pkgrel bump.

[1] https://github.com/FluidSynth/fluidsynth/pull/676

Loading...