Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
On 2021-09-24 19:18:33 +0200, Francesco Poli wrote:
> On Fri, 24 Sep 2021 11:11:27 +0200 Sebastian Ramacher wrote:
>
> [...]
> > I'm unable to reproduce the crash on an updated bookworm installation.
>
> First of all, thank you so much for your very prompt reply!
> That's really appreciated.
>
> It's unfortunate (especially for me!) that you do not experience the
> segfault that I see... :-p
>
> I tried to figure out which exact package upgrade is the cause of the
> regression on my box. In order to do so, I re-upgraded all the packages
> I had upgraded (and then downgraded again...) this morning. One small
> set of related packages at a time.
> Now I have only 1 package left to upgrade: libglibmm-2.4-1v5
>
> If I upgrade that package too:
>
> # aptitude --purge-unused safe-upgrade
> The following packages will be upgraded:
> libglibmm-2.4-1v5
> 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> [...]
>
> I get the segfault:
>
> $ jackd --realtime -d alsa --device hw:PCH --softmode --hwmeter --rate 44100 &
> jackdmp 1.9.19
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2016 Grame.
> Copyright 2016-2021 Filipe Coelho.
> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> no message buffer overruns
> no message buffer overruns
>
> [1]+ Segmentation fault jackd --realtime -d alsa --device hw:PCH --softmode --hwmeter --rate 44100
>
> If I downgrade that package again:
>
> # dpkg -i /var/cache/apt/archives/libglibmm-2.4-1v5_2.64.2-2_amd64.deb
> dpkg: warning: downgrading libglibmm-2.4-1v5:amd64 from 2.66.1-1 to 2.64.2-2
> [...]
>
> I no longer get any segfault:
>
> $ jackd --realtime -d alsa --device hw:PCH --softmode --hwmeter --rate 44100 &
> jackdmp 1.9.19
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2016 Grame.
> Copyright 2016-2021 Filipe Coelho.
> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> no message buffer overruns
> no message buffer overruns
> no message buffer overruns
> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> audio_reservation_init
> Acquire audio card Audio1
> creating alsa driver ... hw:PCH|hw:PCH|1024|2|44100|0|0|nomon|hwmeter|soft-mode|32bit
> configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
> ALSA: final selected sample format for capture: 32bit integer little-endian
> ALSA: use 2 periods for capture
> ALSA: final selected sample format for playback: 32bit integer little-endian
> ALSA: use 2 periods for playback
>
> and jackd seems to work correctly (tested with audacious output,
> I can listen to music without any issue).
>
> Hence, it seems that the bug is in libglibmm-2.4-1v5/2.66.1-1 .
> Now I wonder why you are not experiencing the same bug...
>
> > Could you please provide a backtrace of the crash so that we can try to
> > pinpoint the problem?
>
> I can try to do so.
> Could you please assist me?
>
> I would like to use the new method that loads debugging symbols from
> the Debuginfod server, but I have never done so before...
> Should I follow [instructions] on the Debian Wiki?
I haven't tried that yet, but otherwise you can always install -dbgsym
packages until all symbols are resolved.
Cheers
>
> [instructions]: <https://wiki.debian.org/HowToGetABacktrace>
>
>
> --
> http://www.inventati.org/frx/
> There's not a second to spare! To the laboratory!
> ..................................................... Francesco Poli .
> GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
--
Sebastian Ramacher
Reply to: