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

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

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

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

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

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

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

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

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

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

Solving this requires adding Depends: python3-libusb1

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

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

Processed: severity of 1066599 is important

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

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

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

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