Package: fluidsynth Version: 2.4.0-1 Followup-For: Bug #1053245
More progress on this after editing its service file to replace: After=pipewire.service by: After=pipewire.socket But then there is a conflict with Debian-gdm having one fluidsynth running that blocks the user one during the opening of the session. So here is what I have done: - kill the corresponding Deabin-gdm process by switching to tty, - then log in after a while so that (tty) user session vanished. fluidsynth should not be enabled by Debian-gdm or any type of system user, or default for any user. And let users activate it for their sessions. -- 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
