Bug#1053245: fluidsynth: Fluidsynth starts at boot and blocks the sound device, no obvious way to disable it

[Alban Browaeys]

On Thu, 2 Nov 2023 23:05:28 +0100 at46  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

Bug#1067562: FTBFS: missing symbols on 32-bit architectures

[Thomas Orgis]

Am Wed, 03 Apr 2024 20:46:29 +0200
schrieb Simon Chopin : 

> I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
> start the t64 transition for this package, based on the following
> comment:

Are you able to test this for the dev snapshot of mpg123 before I do
the next release?

http://mpg123.org/snapshot/mpg123-1.32.6-dev+20240403022201.tar.bz2

This gets rid of the ambiguous symbols for this type of build (or
should, at least), leaving only those with 64 and _64 suffix (where
applicable).

This at least avoids the subtle memory-corrupting ABI mismatch. Any
binaries built with enabled large file support continue to work,
anyway. That ABI is stable.

If I get an OK that this really fires as supposed on Debian builds,
I'll release 1.32.6.


Alrighty then,

Thomas

Bug#1067562: FTBFS: missing symbols on 32-bit architectures

[Simon Chopin]

Source: mpg123
Followup-For: Bug #1067562
X-Debbugs-Cc: scho...@ubuntu.com
Control: tags -1 ftbfs patch

Hi,

I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
start the t64 transition for this package, based on the following
comment:

> the non-suffixed functions now work with 64 bit offsets, where they
> formerly worked with 32 bit off_t arguments. This could be considered
> ABI breakage, too.

That's definitely an ABI break, so the transition is necessary in any
case. We can always add back the compat layer if we deem it necessary.


-- System Information:
Debian Release: trixie/sid
  APT prefers noble-updates
  APT policy: (500, 'noble-updates'), (500, 'noble'), (100, 'noble-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-20-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
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
diff -Nru mpg123-1.32.5/debian/changelog mpg123-1.32.5/debian/changelog
--- mpg123-1.32.5/debian/changelog  2024-03-31 10:08:02.0 +0200
+++ mpg123-1.32.5/debian/changelog  2024-04-03 20:29:56.0 +0200
@@ -1,3 +1,13 @@
+mpg123 (1.32.5-1ubuntu1) noble; urgency=medium
+
+  [ Steve Langasek ]
+  * Rename libraries for 64-bit time_t transition. (Closes: #1063140)
+
+  [ Simon Chopin ]
+  * Only include 32bit compat symbols on i386 arches (Closes: #1067562)
+
+ -- Simon Chopin   Wed, 03 Apr 2024 20:29:56 +0200
+
 mpg123 (1.32.5-1build2) noble; urgency=medium
 
   * No-change rebuild for CVE-2024-3094
diff -Nru mpg123-1.32.5/debian/control mpg123-1.32.5/debian/control
--- mpg123-1.32.5/debian/control2024-03-12 07:39:44.0 +0100
+++ mpg123-1.32.5/debian/control2024-04-03 20:20:46.0 +0200
@@ -43,7 +43,10 @@
  OSS4, the Advanced Linux Sound Architecture (ALSA), JACK, PortAudio,
  PulseAudio, OpenAL and the Network Audio System (NAS).
 
-Package: libmpg123-0
+Package: libmpg123-0t64
+Provides: ${t64:Provides}
+Replaces: libmpg123-0
+Breaks: libmpg123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -57,7 +60,10 @@
  This package contains the C libraries needed to run executables that use
  the mpg123 library.
 
-Package: libout123-0
+Package: libout123-0t64
+Provides: ${t64:Provides}
+Replaces: libout123-0
+Breaks: libout123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -70,7 +76,10 @@
  .
  This package contains the shared out123 library.
 
-Package: libsyn123-0
+Package: libsyn123-0t64
+Provides: ${t64:Provides}
+Replaces: libsyn123-0
+Breaks: libsyn123-0 (<< ${source:Version})
 Multi-Arch: same
 Architecture: any
 Section: libs
@@ -88,9 +97,9 @@
 Architecture: any
 Section: libdevel
 Depends:
- libmpg123-0 (= ${binary:Version}),
- libout123-0 (= ${binary:Version}),
- libsyn123-0 (= ${binary:Version}),
+ libmpg123-0t64 (= ${binary:Version}),
+ libout123-0t64 (= ${binary:Version}),
+ libsyn123-0t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: MPEG layer 1/2/3 audio decoder (development files)
  mpg123 is a real time MPEG 1.0/2.0/2.5 audio player/decoder for layers
diff -Nru mpg123-1.32.5/debian/libmpg123-0.install 
mpg123-1.32.5/debian/libmpg123-0.install
--- mpg123-1.32.5/debian/libmpg123-0.install2023-10-01 15:44:05.0 
+0200
+++ mpg123-1.32.5/debian/libmpg123-0.install1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-usr/lib/*/libmpg123.so.0*
diff -Nru mpg123-1.32.5/debian/libmpg123-0.lintian-overrides 
mpg123-1.32.5/debian/libmpg123-0.lintian-overrides
--- mpg123-1.32.5/debian/libmpg123-0.lintian-overrides  2023-10-01 
15:44:05.0 +0200
+++ mpg123-1.32.5/debian/libmpg123-0.lintian-overrides  1970-01-01 
01:00:00.0 +0100
@@ -1,2 +0,0 @@
-# The SSE, 3DNowExt, 3DNow, and MMX decoders use non-pic assembly code.
-libmpg123-0 [i386]: specific-address-in-shared-library
diff -Nru mpg123-1.32.5/debian/libmpg123-0.symbols 
mpg123-1.32.5/debian/libmpg123-0.symbols
--- mpg123-1.32.5/debian/libmpg123-0.symbols2023-10-02 21:38:58.0 
+0200
+++ mpg123-1.32.5/debian/libmpg123-0.symbols1970-01-01 01:00:00.0 
+0100
@@ -1,160 +0,0 @@
-libmpg123.so.0 libmpg123-0 #MINVER#
- mpg123_add_string@Base 1.6.2
- mpg123_add_substring@Base 1.6.2
- mpg123_chomp_string@Base 1.15.1
- mpg123_clip@Base 1.6.2
- mpg123_close@Base 1.6.2
- mpg123_copy_string@Base 1.6.2
- mpg123_current_decoder@Base 1.7.2
- mpg123_decode@Base 1.6.2
- mpg123_decode_frame64@Base 1.32.3
- mpg123_decode_frame@Base 1.6.2
- mpg123_decode_frame_64@Base 1.13.7
- mpg123_decoder@Base 1.6.2
- mpg123_decoders@Base 1.6.2
- mpg123_delete@Base 1.6.2
- mpg123_delete_pars@Base 1.6.2
- mpg123_delete_string@Base 1.26.0
- mpg123_distversion@Base 1.32.3
- mpg123_enc_from_id3@Base 1.9.1
- mpg123_enc_from_id3_2@Base 1.28.0
- 

Processed: Re: FTBFS: missing symbols on 32-bit architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs patch
Bug #1067562 [src:mpg123] FTBFS: missing symbols on 32-bit architectures
Added tag(s) patch.

-- 
1067562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 1068293 to flowblade: 2.14 missing Depends on python3-libusb1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1068293 flowblade: 2.14 missing Depends on python3-libusb1
Bug #1068293 [flowblade] flowblade: 2.14 fails to launch due to missing app.py
Changed Bug title to 'flowblade: 2.14 missing Depends on python3-libusb1' from 
'flowblade: 2.14 fails to launch due to missing app.py'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1068293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068293: flowblade: 2.14 fails to launch due to missing app.py

[Martin-Éric Racine]

Solving this requires adding Depends: python3-libusb1

Bug#1068114: libfluidsynth-dev: package dependencies incongruent with libfluidsynth

[fabian]

Am 03.04.2024 01:22, schrieb Gravis:
Since you are basing dependencies on the generated pkg-config file then 
this
means that the libfluidsynth-dev package is built with 
enable-systemd=on while

the libfluidsynth package is being built with enable-systemd=off


What makes you think it is built without systemd support?

This is an excerpt from the build log:

"""
Miscellaneous support:
  D-Bus: yes
  LADSPA support:yes
  LASH support:  no
  NETWORK Support:   yes
IPV6 Support:yes
  Readline:  yes (NOTE: GPL library)
  systemd:   yes
  getopt:yes
"""

https://buildd.debian.org/status/fetch.php?pkg=fluidsynth=amd64=2.3.4-1%2Bb3=1711274976=0

 - Fabian

Processed: severity of 1066599 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1066599 important
Bug #1066599 {Done: Sebastian Ramacher } 
[src:libquicktime] libquicktime: FTBFS: qtpng.c:74:5: error: implicit 
declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1066599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068293: flowblade: 2.14 fails to launch due to missing app.py

[Martin-Éric Racine]

As see in 
:

"Distro packagers, please see info on the needed configuration file
addition (/etc/udev/rules.d/90-flowblade.rules) described in the link
to docs above."

Martin-Éric

Bug#1063140: mpg123: NMU diff for 64-bit time_t transition

[Thomas Orgis]

Hi again,

(after Easter hiatus … or rather xz backdoor meltdown?)

I had a stab at this, detecting a system that forces 64 bit offsets on
a 32 bit base in configure. This is to ensure that you do not encounter
the same symbol (like mpg123_tell() on two builds of the library on the
same platform offering a differing ABI (32 or 64 bit argument or return
value).

This is supposed to look like that:

$ CPPFLAGS=-D_FILE_OFFSET_BITS=64 ./configure
[…]
checking switched off_t size... 8
checking unswitched off_t size... 4
checking size of off_t... 8
configure: Detected system with enforced 64 bit offsets, dropping suffixless 
symbols for uncryptic ABI breakage.
checking if native off_t is already 64 bits... yes
[…]
  default offsets . 64
  explicit 64 bit offsets . no
  forced 64 bit offsets ... yes
[…]

This removes the ambiguous symbols from libmpg123.so and libsyn123.so.
With unchanged soversion, client code built for the earlier version
before the off_t/time_t 64 bit switch will fall in two categories:

1. Built with enabled large file support: Continues to work, no
   breakage.

2. Built without large file support: Will break early at runtime
   linking stage.

There might be applications that just use API not affected by off_t
changes and thus are fine either way.

Can you verify that the prospective 1.32.6 (named 1.32.6-dev) under

http://mpg123.org/snapshot/mpg123-1.32.6-dev+20240403022201.tar.bz2

works fine in the debian build and meets expectations? I'd do a proper
release of it soon, then.

It's up to you (Debian) to decide what to do with binary package naming
for the transition (it is your business anyway;-), but I feel strongly
about the change to avoid an existing symbol changing ABI with subtle
breakage. I also think it is reasonable not to invest work into yet
another set of wrappers to put 32 bit offsets on life suppport on a
system that follows the decision to enforce 64 bits. The setup of
wrappers and alias calls in mpg123 code is confusing enough already.


Alrighty then,

Thomas