Bug#829434: mpg123 segfaults once after dist-upgrades

On Jul 03, Thomas Orgis wrote: > You still see the jack errors and get a segfault? Are you able to > create a backtrace? (`ulimit -c unlimited` before running mpg123 and > then analysing the core file with gdb)? No, I cannot reproduce this at will: I have only noticed

Bug#829434: mpg123 segfaults once after dist-upgrades

Am Sun, 3 Jul 2016 13:32:20 +0200 schrieb Marco d'Itri : > > mpg123 -o alsa [your flags] > I see no new/specific output by adding -o alsa. You still see the jack errors and get a segfault? Are you able to create a backtrace? (`ulimit -c unlimited` before running mpg123 and then

Bug#829434: mpg123 segfaults once after dist-upgrades

On Jul 03, Thomas Orgis wrote: > This looks like the jack output module crashing, a bug in itself, that > might be fixed in the current upstream mpg123. Your main issue is that > the proper output module, alsa in this case, fails to work. What is the > output of > >

Bug#829434: mpg123 segfaults once after dist-upgrades

Am Sun, 3 Jul 2016 12:14:40 +0200 schrieb Marco d'Itri : > mpg123 --random --quiet --control --title ... > > [jack.c:252] error: Failed to open jack client: 0x1 > [jack.c:58] warning: FIXME: One needs to wait or write some silence here to > prevent the last bits of audio to

Bug#829434: mpg123 segfaults once after dist-upgrades

Package: mpg123 Version: 1.22.4-1 Severity: normal This has happened multiple times to me after a dist-upgrade, but I do not know exactly how to reproduce it: mpg123 --random --quiet --control --title ... [jack.c:252] error: Failed to open jack client: 0x1 [jack.c:58] warning: FIXME: One needs