Fluidsynth crashes since 2.4.5. # journalctl --user -b0 -u fluidsynth avril 23 13:15:38 tuxmachine systemd[1800]: Starting fluidsynth.service - FluidSynth Daemon... avril 23 13:15:38 tuxmachine touch[1832]: touch: impossible de faire un touch '/run/lock/fluidsynth/fluidsynth.lock': Aucun fichier ou dossier de ce n> avril 23 13:15:38 tuxmachine systemd[1800]: fluidsynth.service: Control process exited, code=exited, status=1/FAILURE avril 23 13:15:38 tuxmachine systemd[1800]: fluidsynth.service: Failed with result 'exit-code'. avril 23 13:15:38 tuxmachine systemd[1800]: Failed to start fluidsynth.service - FluidSynth Daemon. I sent a bug report https://github.com/FluidSynth/fluidsynth/issues/1527. The issue has been resolved, but it appears that a fluidsynth.tmpfiles need to be added to the rpm. Reproducible: Always
Thank you for the report. If you create the file "/usr/lib/tmpfiles.d/fluidsynth.conf", with the following content: d /run/lock/fluidsynth 0777 root root Does this help?
Yes,actually creating this file solves the problem. It seems that in the git directory there is a spec file with the modifications to be made. https://github.com/FluidSynth/fluidsynth/commit/f8cdcb846b5c7c32a1de99db0ff69c4841142a99
Thank you, fix is on the way.
FEDORA-EPEL-2025-4b386dcec9 (fluidsynth-2.4.5-2.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-4b386dcec9
FEDORA-EPEL-2025-7cf881eee3 (fluidsynth-2.4.5-2.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7cf881eee3
FEDORA-2025-76dcc485e0 (fluidsynth-2.4.5-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-76dcc485e0
FEDORA-2025-08db84da4f (fluidsynth-2.4.5-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-08db84da4f
FEDORA-EPEL-2025-4b386dcec9 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-4b386dcec9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-7cf881eee3 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7cf881eee3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-76dcc485e0 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-76dcc485e0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-76dcc485e0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-08db84da4f has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-08db84da4f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-08db84da4f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-4b386dcec9 (fluidsynth-2.4.5-2.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-7cf881eee3 (fluidsynth-2.4.5-2.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-08db84da4f (fluidsynth-2.4.5-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-76dcc485e0 (fluidsynth-2.4.5-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.